Your involvement in setting up a Community test cycle will vary based on your purchase order entitlements. Frequently, your Applause team will create and activate your test cycle, where your work may only involve reviewing the changes made before a cycle launches.

If you’d like a more hands-on approach to creating your test cycles, the Applause platform will support that as well.

Note: With either approach, once the test cycle is set up, your Applause management team will be responsible for activating it.

Cycle Creating Options in the Applause Platform

You can create a test cycle in two ways:

• Create a new test cycle from scratch
• Copy (Clone) an existing one

How to Create a New Test Cycle

1. Select a product from the product picker in the left side navigation menu.
2. From the left navigation, select “Test Cycles”.
3. Select the “New Test Cycle” button at the top of the page. The new Test Cycle wizard will open consisting of 3 simple steps: Overview, Scope and Configuration.

 

Overview

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

Test Cycle Name

Give your cycle a name that has meaning, character and personality. 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/16/2020

Testing Type

Applause offers different types of testing. Your entitlements will determine which ones are available to you.

Product Being Tested

Select the product you are asking to be tested from the list of your pre-defined products.

Build Being Tested

Select the product build to be tested, either from the list of your pre-defined builds or create a new one as we described in the Product Builds section.

Development Stage

Select the Development Stage of the build.

Testing Frequency (Only Applicable to Functional Testing)

• Single - A targeted, one-time testing cycle
• Continuous - A recurring testing cycle with multiple builds. Learn more about the differences here

Note: You should confirm any entitlement restrictions on the testing frequency with your Applause management team.

Testing Date Range

This timeframe should be chosen in consultation with your Applause management team. Generally, test cycles last around 3 days, but this can vary a lot depending on your product and testing needs.

Once done, click “Next” to continue.

 

Scope

The Scope section allows you to set the specifics of your testing needs and consists of two sections: Testing Coverage and Testing Scope.

Testing Coverage

In the Testing Coverage area, you can limit the coverage of the testing based on Regional Requirements (geolocation and language) and Platform & Environments (hardware, operating system and browsers). Testers invited to participate in the test cycle will adhere to these settings.

Testing Scope

The Testing Scope section allows you to add essential testing features to your test cycle, such as Exploratory Testing, Test cases, Known Issues & BFV. and Reviews.

You need to click on the add button to utilize the specific features. Let's discuss how to work with each of these features individually.

Exploratory Testing

This section includes a collection of fields where you can give details about what the testing should cover. Your Applause management team can help advise on the content for these fields.

App Components

If app components have been added to the product and need to be enabled, click on the “Use App Components to help define scope” button.

This is where you can define what areas are in scope for testing. It is always best to start with a brief statement as to the testing focus. You can also include information on which types of bugs would be most valuable, any special new features that should be highlighted and any testing environment information that wasn’t covered in the previous section.

This is where you cover what should not be included in testing. The content often includes Known Issues, OOS testing types (e.g. usability, localization), OOS areas and forbidden actions (e.g. using fake data).

Here you can specify any requirements for the issue reports. These can include a specific format for the issue report title, required account information, specific attachments (like logs and screenshots) and any other relevant items.

Defines test case claiming, time limits and other rules to claim and submit a test case. Your Applause management will typically handle this field.

Information about your Applause team and ways to reach them. The Applause management team will fill in this field.

Informs about anything else needed, usually tips on how to get console logs or other educational materials.

Custom fields allow you to collect additional information from testers when they submit a bug. Each test cycle can contain a different set of required custom fields.

To add a custom field, click the “Add New Field” button and fill out the 3 fields with the required information. Testers will see all the 3 fields:

• Field Label
• Explanation on How to Obtain the Information
• Field Type to enter the information

Once completed, select “Done” to return to the scope section.

Note: You still must to save the test cycle in order for your changes to be saved.

Test Cases

In the Test Cases area, you may select test cases from the list pre-defined for the tested product to include in the cycle. You will learn how to create new test cases in the next section.

How to Assign a Test Case to the Test Cycle

When clicking Add Test Cases for the first time, you will be redirected to the Test Case Management page where you need to select test cases and add them to the test cycle.

When editing the test cases the next time, they’re opened inside the test cycle, without redirecting you to the Test Case Management page.

Here you can select relevant test cases to assign them to the cycle or unselect test cases.

• Unchecking the “Show Only Selected” checkbox will show all the test cases of the product.
• Select “Done” to return to the Scope section.

Note: You still need to save the test cycle in order for your changes to be saved.

Known Issues and 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). We will learn more about management of Known Issues here. 

You can mark Known Issues that were fixed for the tested product build so that the testing community can verify the fix is properly working.

How to Assign Known Issues and BFVs to Your Test Cycle

1. While in the Known Issues & BFV area, locate the relevant previously reported Known Issues to assign.
2. Check the “Known Issues” box for the relevant Known Issues to assign Known Issues.
3. Check the “Request Verification” box for the relevant Known Issues to assign BFVs.
4. Select “Done” to return to the scope section.

App Review

In the App Review area, you can request testers to complete a review of your product. There is a default of seven questions, however you may edit, reorder, delete and add questions as needed.

Make sure to select “Done” once all settings are in place and click the “Next” button to continue.

 

 

Configuration

In the Configuration section, you can apply advanced settings for your test cycle.

Export

Check if you would like to have issues automatically exported to your Bug Tracking System (BTS) after they are approved. You can learn about exporting issues to BTS here.

Attachments

You can choose to require attachments in the form of screenshots, logs and other evidence for the issue reports. This is recommended. Set the maximum file size to accommodate your BTS.

Non-Disclosure Agreement

You can require testers to accept a custom NDA in order to participate in testing. Review this option with your Applause management team prior to enabling it.

Chat

This setting creates a chat room to facilitate communication during testing. This should be enabled by default and should stay enabled unless otherwise arranged with the Applause management team.

Test Cycle Attachments

You can upload files that 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 and other related items.

Once done, click “Finish” to complete the test cycle creation and your draft will be saved in the platform.

 

How to Activate Test Cycles

Once the new test cycle is created, your Applause management team is responsible for activation. You may contact your Applause team via phone or email, but you may also request the cycle activation from the Applause platform.

How to Request Cycle Activation from the Applause Platform

1. While in the Test Cycle list page click on the Request Activation button in the desired row.
2. Or open the relevant test cycle, and from the Actions dropdown menu select “Request Activation”.