You're viewing help content for version:
- 6.2
- Older Versions
-
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.
- 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:
-
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