Define appropriate status field values
The status field can be used as a great resource to track the progress and readiness of entities. As a Project Administrator, think about your organization's governance and tracking needs and appropriately set up these status values. Make sure the team consistently tracks the status up to date for all entities.
Order the status list options in a logical sequence of progress indications. Specifically, the first Status list option is used by default, for all the newly created entities. For example, consider the list below (in that order):
- Work In Progress
- Under Review
Each Status list option has an attribute that indicates if an entity in that particular status can be considered ready for test execution. This readiness indicator attribute is used as one of the parameters when calculating the Test Suite readiness. Following a consistent approach here will provide great guidance on your Sprint or Release progress.
In the above list, if you believe only "Completed" entities can be considered as "Ready", indicate appropriately.
Make use of Application Environments
ACCELQ supports the concept of Application Environments to mirror multiple deployment environments you may have in your product development process. As you promote the build between different environments, this feature allows you to seamlessly execute the same scripts without intervention.
Defining the list of Application Environments is the first step in this process. A Project Admin can review and set up the environments based on the specific project need.
Once defined, Application Environments allow you to abstract the data differences between different environments such as Prod, Test, and Dev. Test execution in ACCELQ should be completely hands-free without requiring any environment-specific updates when you run the tests. You can also conditionalize action logic based on the environment name.