Configuration and Customisation


Carry out User Acceptance Testing (UAT)

Have the users validate that the application performs in a way that meets their needs.
  • Application installed
  • Configurations
  • Customisation
  • Converted Data
    1. Install the full application with configurations and customisation.
    2. Load data.
    3. Carry out testing as per the test plan.
    4. Identify and rectify defects.
    5. Retest the application after defect removal.
    6. Sign off the application as ready to go into production.
  • Application tested and ready for a final conversion.

All components need to be loaded into a test environment that will closely resemble the final production environment. If testing is to include performance testing, this will probably be the final environment. If testing is going to include remote testing, there will likely be software to be loaded at remote sites.

All users involved in testing should be set up with correct user access. Setting up users is typically part of the UAT and any issues identified should be treated as other defects are treated.

The use of the defect log is essential to track the status of defects. It can quickly get out of control if a number of people are informally referring questions to the development team. Defects can get lost, and forgotten. The status of rectifications can also get out of control and it becomes unclear what is still outstanding. The defect logging form will also form a single point of reference for each defect. It contains the key information needed to understand the problem.

UAT should be aligned to the business processes. The processes should be tested to ensure they align with how the system is configured. It is useful to walk through each process to ensure the results are as expected. It may result in modifications to the process, or changes to the application.

There will need to be someone coordinating the testing. It cannot be left to a group of people to test their own part and sign it off. For example, regression testing should be coordinated. If there are a number of changes that impact the same part of the application, it is probably sensible to regression test them all together rather than separately.

Defect Logging Form Form to record each defect
Defect Log Log of all defects identified and their status

Return to the top