Open Category List

Creating a Test Cycle

8 minutesread

Your involvement in setting up a test cycle will vary based upon your purchase order entitlements. Frequently, your Applause Team will be involved with creating and activating your test cycle, where your work may only involve reviewing the changes made before a cycle launches. But, if you’d like a more hands-on interaction with creating your test cycles to become more self-sufficient, the Applause Platform will support that as well. Regardless, please note that once the test cycle is set up, our Applause team will still be responsible for activating it and engaging with our testing community for selecting your test team.

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. Basic information on already-set test cycles is presented, such as the test cycle name, type and status, as well as breakdown of collected results on issues, test cases and reviews. Learn more about your test cycle management options here.

Creating New Test Cycles

You may create a new Test Cycle from scratch, or ‘copy’ (clone) an existing one.

To create a new test cycle from scratch:

1. While in the Test Cycle List page, click on the New Test Cycle button at the top of the page , and select New Test Cycle.

2. The New Test Cycle wizard opens. The wizard consists of 3 simple steps: Overview, Scope and Configuration. You may only move between the completed steps.

Overview

In the Overview step, you will be asked to provide the general details about your required testing, such as type, frequency, date range, and more.

To complete the Overview step:

1. Type in the test cycle name. As your test cycle list may get crowded over time, make sure to set a name that is specific enough to avoid confusion later. In addition, try to 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”).

2. Select the testing type. Reference your Statement of Work with Applause if you need to confirm what testing type purchased, or simply verify with your Applause team. This will prevent confusion or incorrect testing performances being run against your product.

3. Select the product you’re asking to be tested from the list of your pre-defined products. Learn more about managing your products here

4. Select the product build to be tested, either from the list of your pre-defined builds, or create a new one – you’ll be asked to provide its version, changes it introduces, and files / URLs for testers to get it. Learn more about product builds here.

5. Select the Development Stage in which the build is being tested on.  Learn more about use of Development Stages here.

6. Select the testing frequency, as Single or Continuous. Learn more about the differences between Single and Continuous cycles here.

7. Set the testing dates. 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 Applause team if you aren’t sure how long to run a cycle.

Once done, click Next to continue to the second step.

Scope

In the Scope step, you will be able to set the specifics of your testing needs for the product build. There are up to 5 scoping areas to complete, pending on your Statement of Work with Applause and your testing needs: Testing Coverage, Exploratory Testing, Test Cases, Known Issues & BFV, and App Review.

Testing Coverage

In the Testing Coverage area, you can limit the coverage of the testing based on geolocation and technology attributes. Testers invited to participate in the test cycle will adhere to their settings.

Exploratory Testing

In the Exploratory Testing area, you are able to input instructions to testers in an easy to use template, including what is in and out of scope of testing (such as certain screens/pages, or functionalities), formatting and other issue reporting requirements, contact information etc. You are also able to add Custom Fields to the test cycle, allowing you to capture – through the testers – any data about the submitted issue in a structured manner.

Once completed, click on Done to return to the Scope step. Note that you still must save the test cycle in order for your changes to be saved.

Test Cases

In the Test Cases area, you are able to select the test cases to include in the cycle from the list of test cases pre-defined for the tested product. Learn more about how to create new test cases here, and how to manage them into test suites here

To assign a test case to the test cycle:

1. While in the Test Cases area, locate the relevant test cases to assign. You may sort the table, filter by test suites, show or hide any unselected test cases, or run a textual search.

2. Check the “Selected” box next to the relevant test cases.

3. Click on Done to return to the Scope step. Note that you still must save the test cycle in order for your changes to be saved.

Known Issues & BFV

In the Known Issues & BFV area, you are able to manage the list of already-found issues in your product to be available to the testers (thus preventing duplicate submissions). Learn more about management of Known Issues here. In addition, you’re able to mark Known Issues that were fixed for the tested product build so that the testing community can verify the fix. Learn more about the Bug Fix Verification (BFV) process here.

To assign Known Issues and BFVs to the test cycle:

1. While in the Known Issues & BFV area, locate the relevant previously reported known issues to assign. You may sort the table, filter by test cycle and BFV status, or run a textual search.

2. Check the “Known Issues” box next to the relevant known issues to assign Known Issues.

3. Check the “Request Verification” box next to the relevant known issues to assign BFVs.

4. In case any of the selected Known Issues was collected in a test cycle that required testers to accept a Non-Disclosure Agreement (NDA), you’ll be required to upload a matching NDA for the current test cycle. Testers will be required to accept it before gaining access to the cycle.

5. Click on Done to return to the Scope step. Note that you still must save the test cycle in order for your changes to be saved.

Make sure to click on Done once all settings are in place. Note that you still must save the test cycle in order for your changes to be saved.

App Review

In the App Review area, you are able to request that testers will complete a review of your product. There is a default of seven questions, however you may edit, reorder, delete, and add questions as needed. Learn more about App Reviews here.

Make sure to click on Done once all settings are in place. Note that you still must save the test cycle in order for your changes to be saved.

Configuration

In the Configuration step, you are able to apply advanced settings for your test cycle.

To complete the Overview step:

1. Apply the following settings:

  • Export: Check if you would like to have issues automatically exported to your Bug Tracking System (BTS) as soon as they are approved. Learn more about exporting issues to BTS here.
  • Attachments: Check if you would like to mandate file attachments to every issue report, and set maximum size which may be a requirement for your BTS.
  • Non-Disclosure Agreement: Check if you would like to mandate the testers accepting your NDA as they accept the test cycle, and upload your NDA file.
  • Chat: Check if you would like to create a chat room for the cycle, where you, the Applause team and testers may converse during testing.
  • Test Cycle Attachments: Upload whatever other files might be useful for the testers. This may include your product manual, a short video where you review the changes implemented in the tested build, etc.

2. Once done, click on Finish to complete the test cycle creation.

The new test cycle is displayed. Learn more about managing existing test cycles here.

Cloning Test Cycles

Quite commonly, you’ll be testing the same product over and over again as your team is working on new builds. As a result, most of your test cycle may be set relatively similarly. In those cases, it should be more efficient to create a new cycle by cloning (copying) an existing one, which will move many of the existing cycle settings into the new one.

To clone a test cycle:

1. While in the Test Cycle List page, click on the New Test Cycle button at the top of the page , and select Copy Test Cycle.

2. The Copy Test Cycle dialog box is open. Search for the existing test cycle by its name or ID.

3. Click Continue.

4. Set the cloning definitions of the new cycle, including its new name and which existing attachments and sections to move to it.

5. Click Copy.

The new test cycle is displayed in the Edit mode. You may now apply any setting not copied from the existing cycle and whatever other changes needed.

Alternatively, you may also clone a cycle in the following way:

  • From the Test Cycle List by clicking on the Actions button next to the relevant existing cycle and selecting Copy Test Cycle
  • From the Test Cycle Details by again clicking on the Actions button and the top right of the page and selecting Copy Test Cycle.

Activating the New Test Cycle

Once the new test cycle is created you may want to activate it to start testing. Your Applause team will need to get involved in that, as they review your test cycle setting, identify the best testers to match your needs, ensure your cycle settings are aligned with your testing strategy, goals and Statement of Work, etc. You may contact your Applause team via phone or email, but you may also request the cycle activation from the Applause Platform.

To request cycle activation:

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.

2. Click on the Actions button next to the relevant existing cycle and select Request Activation (based on your user permissions, you might see this option as “Activate Test Cycle”

Alternatively, you may also request cycle activation from the Test Cycle Details, by again clicking on the Actions button at the top right of the page, and selecting Request Activation (or Activate Test Cycle).

0
0
803
8 minutesread

Related Knowledge Base Posts