As you manage your test cycles in the Applause Platform, you will notice the status of each cycle is indicated in the Test Cycle List, Test Cycle Details and other pages.
Your test cycles can be in any of the following statuses:
- Draft: A created, not yet activated, test cycle.
- Pending Activation: A Draft cycle that its activation was requested.
- Active: An in-progress cycle with allowed testing and triage.
- Locked: An in-progress cycle with completed testing and allowed triage.
- Closed: A completed cycle.
It is clear, thus, to see the difference between a “Locked” and a “Closed” test cycle. While the testing activity is essentially stopped for the Locked cycle, the work on the cycle is still in progress. Indeed testers are not able to log any new bugs or execute additional test cases, but the triage may very well still be in progress, and you and your Applause team can – and should – still review incoming results, approve or reject it, and export where applicable. You may even edit the cycle settings (or upload a new build for a continuous cycle) and re-activate it if needed.
A closed cycle, on the other hand, is a more terminal state for the cycle, in which both testing and triage are not allowed. Note that you can still view and export results even after the cycle has been closed.
As you may expect, over time you’ll have and increasing number of closed test cycles, while most of your interaction in the Applause Platform will be with cycles on other statuses. That is why several lists – such as the Issue List and Test Cycle List offer filters that by default exclude closed test cycles from the display.