As you test your products in the Applause Platform, test cycles will be created, activated, executed, locked, and – ultimately – closed. Your test cycle management needs may change according to the cycle status: for active test cycles you most probably be interested with time left until closed and the number of issues and test case results still pending triage, with locked cycles your focus will probably towards the collected results, whereas closed cycles might only interest you if you intend to clone them.
The Applause Platform offers a simple view of your test cycles, helping you to fulfill your changing management needs.
Viewing the Test Cycle List
To view the Test Cycle List:
1. Log in to the Applause Platform and navigate to Test Cycles.
The Test Cycle List will be displayed.
Note that by default the list will hide all Closed test cycles. To show the Closed test cycles, check the box next to Show Closed Cycles.
Understanding Test Cycle Attributes
The following attributes are presented for each test cycle:
- Testing Type: The nature of testing executed in the cycle – Fn (Functional), Ux (Usability), Ac (Accessibility), etc.
- ID: The internal identifier of the test cycle.
- Name: The test cycle name.
- Click on the Test Cycle Name to move to the Test Cycle page and view more details.
- Type: Any of the following:
- Single (a targeted, one-time testing)
- Continuous (a recurring, repetitive testing. Learn more about the differences between Single and Continuous cycles here)
- Bug Fix Verification (an automatically-created cycle dedicated for verification of fixed known issues)
- Status: Any of the following:
- Draft (a created, not yet activated, test cycle)
- Pending Activation (a Draft cycle whose 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).
- Issues: Current count of collected issues:
- (new issues, waiting triage)
- (pending issues, with triage recommendation set by the testing community)
- (total number of collected issues)
- Test Case Results
- (pending test case results, waiting triage)
- (in progress test cases)
- (passed test cases)
- (failed test cases)
- Reviews: Number of tester reviews collected. Learn about how to ask the testers to review your product here.
- Time Left: Indication for Active cycles on time left until planned cycle close date & time.
Test Cycle Details & Status
There’s much more details and status available for the test cycle than what’s offered in the Test Cycle List. As before, your needs from viewing such additional details may vary based on the Test Cycle Status.
To view the complete test cycle details:
- While in the Test Cycle List page, locate the relevant test cycle. You may sort the table, show or hide the Closed cycles, or run a textual search.
- Click on the Test Cycle name.
The Test Cycle Details page will be displayed. The page consists of several tabs, which may vary based on the testing scope offered in the cycles. The tabs include:
- Overview tab
- Summary tab
- Issues tab
- Test Case Results tab
- Test Case Coverage tab
- Reviews tab
- Known Issues tab
Overview Tab: Test Cycle Settings
The Overview tab contains the setting highlights of the test cycle, including the tested build, testing methodology, in/out of scope definitions, test cases included, and more.
Summary Tab: Testing Status
The Summary tab contains the most up-to-date status of the cycle run. Such include:
- Summary of bug distribution across status (if pre-triage), value (if approved) or rejection reason (if rejected).
- Breakdown of reported issues by product component and status, value or rejection reason.
- Triage status and Testing Team Lead activities.
- Breakdown of reported issues by type and severity/
- Device coverage, either mobile or desktop.
- Issue source, either exploratory or structured testing.
The following tabs allow you to view and interact with the results collected during the cycle execution by the testing community.
- Learn more about how to manage the cycle results here.
- Learn more about how to manage known issues here.
Performing Actions on Test Cycles
As you manage your test cycle, you will be able to perform different actions.
To perform actions on the test cycle:
1. While in the Test Cycle List page, locate the relevant test cycle. You may sort the table, show or hide the Closed cycles, or run a textual search,
While in the Test Cycle Details page, locate the Actions button on the top right corner.
2. Click on the Actions button, and select an action.
The following actions are available:
- Edit: Modify the test cycle settings. Note that applying edits to an Active test cycle will result with an email sent to all cycle participants, notifying them on the changes.
- Request Activation / Activate: Start testing activity for the cycle. Pending your permissions you may be able to activate on your own, or request the activation from your Applause team.
- Lock: Stop testing activity for the cycle. While no new issues can be reported or test cases executed, triage is still allowed. Note that a test cycle will be locked automatically based on its predefined schedule.
- Request Closure: Complete all testing and triage activity for the cycle. While ne new issues can be reported, test cases executed or triage allowed, you are still able to export issues to external file and your Bug Tracking System.
- Reactivate: Resume testing activity for the cycle. At times it is required to reactivate the cycle after it has been locked. Consult your Applause team if that’s needed.
- New Build: For Continuous Cycles, kick-start a new test run by uploading a new build.
- Copy: Create a new test cycle based on the settings of the existing one. Copying (or: cloning) test cycles allows you to efficiently prepare for a new cycle, and you are able to select what settings will be brought from the existing cycle to the new one.
- Discard: Permanently delete a draft test cycle (only).
The allowed actions may change according to the test cycle status and your permissions: