Please note that, once the initial functional test cycle is set up, you’ll follow up with your PM at that point to begin selecting your test team. Your involvement in setting up a test cycle will vary based upon your order entitlements – frequently, a Project Manager or Test Team Lead is heavily involved with creating and activating a test cycle, where your work may only involve reviewing the changes made before a cycle launches. However, if you’d like a more hands-on interaction with activating your cycles and creating them, your PM will help you learn how to become more self-sufficient.
To begin, you’ll need to log in to the Applause Dashboard. In the Navigation bar on the left, you’ll see an icon with a Product name listed. If the product you want to start a test cycle for is not listed, click in this area to expand the list of your associated products, and then click the desired product in order to make it your active cycle.
After you’ve selected the correct product, the Testing Progress module in your Dashboard will populate with a list of previous cycles, or a notification that you don’t have any test cycles yet.
Creating New Test Cycles
If this is your first test cycle run for this particular product, you’ll need to click the ‘Create New Test Cycle’ button. However, if you’ve run test cycles in the past for this product, you can access a list of your previous cycles by clicking the Test Cases link in the left navigation bar.
Clicking New Test Cycle, will take you through the steps.
Part 1: Overview
Naming Convention: Give your cycle a name that has meaning, character, and personality. Testers will frequently be invited to numerous cycles at the same time, so naming your cycle accurately helps with clarity and avoids confusion. A good test cycle name typically includes the name of your company or product, the type of testing taking place, and the start date. For example:
- Applause, Inc. – New Chat Features – 7/11/2016
- Applause, Inc. – Dashboard Settings – 7.18.2016
Testing Type: Select the correct Testing Type from drop down menu. Reference your Statement of Work with Applause if you need to confirm what testing type purchased, or simply verify with your Project Manager. This will prevent confusion or incorrect testing performances being run against your product.
Product Being Tested: Assign this test cycle to a specific product. It’s important to note that a product does not have to be assigned to the product that is the current active product.
Build Being Tested: Each test cycle that is tied to a specific product must have a unique build number. Upload your build or provide a URL where it can be downloaded. However, not every cycle needs to be tested against a new build – clicking the dropdown that defaults to New Build will allow you to choose from a list of previous builds for this product.
Testing Frequency: A Continuous Cycle allows you to test your product on a regular basis, allowing you to upload new builds for your test team to verify against as you go. A Single Cycle allows you to run one test cycle against your application, allowing for a focus on particular aspects of your product. If applicable, check with your PM for their recommendation on the best option for your needs.
Testing Date Range: Select when you want the test cycle to start and end. As a point of reference, an average test cycle lasts about 2-3 days. This is long enough to give the testers time to do thorough testing but short enough to give you fast turnaround. Consult with your Project Manager if you aren’t sure how long to run a cycle.
Part 2: Scope
The Testing Coverage section allows you to customize specific regions, countries, languages, OS, and other options.
Scope & Requirements is an easy-to-edit template for you to use. This page includes the option to add Custom Fields.
- In Scope: The In Scope section allows you to list what parts of your product are open for testers to work against. It’s better in this section to be as detailed as possible, as this will not only ensure that what is being tested is what you want tested, but it will also allow for you to call for specific focus to be pointed at a particular area of your title.
- Out of Scope: In this optional field, you’ll be able to give a lit of specific instances of parts of the product you do not want tested this cycle. This is beneficial, as this gives your TTL information on which areas are out of scope, allowing them to review bugs more efficiently and say if a bug is valid or not.
- Additional Instructions: An optional field allowing you to list any other instructions you feel are pertinent for your cycle.
- Custom Fields: This section allows you to add new fields to your bug reports from your testers, either by creating new custom fields manually, or selecting from pre-generated fields from a template.
Test Cases: Select the test cases to include in the cycle from the list. These are are defined in the Test Case Management section. See here for instructions on Creating Test Cases in Excel and uploading them to the Platform. Associate specific test cases with your test cycle by checking and unchecking the box to the left of the test case number. You can also type in a specific test case ID via the ‘Filter test case’ field.
Known Issues: Instructions for utilizing Known Issue Management.
App Review: Option to request that testers to complete a review of your product. There is a default list of seven questions. However they can all be customized. Edit, reorder, delete, and add questions to the list of our default Review questions.
Part 3: Configuration
Export: Approved bugs can be exported to your own in-house BTS. Instructions for setting up BTS Integration.
Attachments: Require testers to include attachments for each reported issue.
Non-Disclosure Agreement: If you need testers to sign an NDA, attach it to the test cycle.
Chat: It is recommended to have a chat room on the test cycle.
Test Cycle Attachments: Include any other documentation required for the test cycle.
Cloning Test Cycles
There is one other way to create a cycle, called Cloning. Click the name of one of the cycles in your Testing Progress module on your Dashboard. In the cycle details page, click the Copy button that appears next to the cycles name at the top of the screen.
Clicking the Copy button will prompt you to confirm whether or not you want to copy the test cycle attachments. Please note, this will copy all attachments – builds, known issues lists, and anything else you’ve attached. You may need to edit certain attachments if you select Yes on this pop-up. After advancing through that pop-up, you’re in an identical workflow to the steps above when creating a cycle from scratch. Once completed, contact your PM, and testing can begin!