During Development and Testing

Tracking Bugs and Issues

• There are many tools available for tracking issues (see Overview of Potential Tools), be they bugs, features or organizational issues. Whichever you select it is strongly recommended that:
  • Your tools are accessible to all (relevant) project members; share the information between partner and customer to prevent creating multiple copies of what is basically the same information.
  • You should try to keep it simple; maintain all the information that you need, but keep classification simple (and central) to minimize the maintenance.

Testing Phases

• Testing is crucial to the smooth deployment of a project, so start testing as soon as possible. This can occur at various levels (developer, a separate test team and/or customer staff).
• It is not compulsory for customers to perform testing, but it helps increase their awareness and acceptance of the project.
• An added advantage is that users often define the requirements in terms of past experiences. Giving them experience of an interim release helps ensure they gain hands-on experience of the new project.

Performance Testing

• Performance is a key aspect of any AEM installation as it can affect the entire user experience.
• The target metrics defined at project begin must be tested. For further details on testing performance see:
• How to Monitor Performance
• Best Practices for Quality Assurance

Testing Results

• Any testing team should be allowed to remain neutral and deliver the testing results.
• It is the responsibility of the Project Manager to assess any implications of the results and decide on appropriate action.

Configuration Management

• In addition to the actual project installation, configuration of both AEM and possibly system software will be necessary. Any such changes should be tracked, and documented in sufficient detail to ensure you are fully prepared for testing and deployment.