To ensure effective test automation and streamlined test management within ACCELQ, it is crucial to carefully plan and establish the appropriate Project granularity. Each Project should be tailored to address the testing requirements of a single Application Under Test (AUT) or a set of closely dependent applications that are commonly tested as a unit.
Focus on Application Under Test (AUT)
When creating Projects, center them around the testing needs of a specific AUT or a logically connected group of applications. This focus provides clarity and better maintenance of the test assets related to each application, enhancing the overall testing process.
Maximize Benefits of Project Granularity
A well-planned Project granularity offers numerous advantages:
- Access Control: Fine-tune access permissions at the Project level to ensure that team members have appropriate access to relevant test assets.
- Configuration Management: Manage configurations specific to each application effectively by organizing them into separate Projects. Lot of configuration settings in ACCELQ are set at the level of an individual Project.
- Asset Sharing: Simplify asset sharing by keeping test cases, data, and components within Projects related to the respective applications.
- Test Execution Management: Streamline test execution monitoring and notifications for each AUT without interference from other Projects.
- CI/CD Integration: Facilitate seamless integration with CI/CD pipelines by maintaining Projects independently and aligned with the application scope.
Test Asset volume is not a criterion
The size or quantity of test assets should not dictate Project granularity. ACCELQ efficiently handles any number of test assets within a Project. Hence, avoid breaking down testing requirements into multiple Projects solely based on asset quantity. Instead, leverage filters within the navigator grids to focus on specific items while retaining an optimal Project structure.
Managing Multiple Application Releases
When dealing with multiple releases of an application (AUT), efficiently handle them by creating Branches within a root Project rather than creating multiple independent Projects. This approach ensures better organization and traceability of testing efforts across different releases.