Course 1: Products
Learn how to create and edit products in the Applause platform.
Testing in the Applause platform is organized by test cycles. A test cycle is focused on an individual build of a product. Given this, your first step in setting up testing in the platform is to create entries for the products you want to test.
Log in to the Applause platform and navigate to Products. The Products page will be displayed. Basic information on already-set products is presented, such as the application type, number of tested and untested builds, and last build tested for the product.
- Click on a product name to view additional details:
Activity - Reporting dashboard providing a breakdown of results at the build level, including their calculated Applause Quality Score. Learn more about the Activity Dashboard here, and about the Applause Quality Score here
Product Details - A summary of the product’s settings
Builds - List of builds tested for the product. Learn more about management of product builds here
Select “Products” in the left-hand navigation and then click “Add Product”.
The new product wizard will open consisting of three simple steps: Basic, Integrations and Components.
Provide some initial details to set up the product in the platform.
Set a name that is specific enough to avoid confusion later.
Select the proper type for your product.
Set the user teams that will have access to the product test cycles. We already discussed this in the User Management section. If you do not wish to limit access, make sure to select the default “All Users” team.
Define the format in which your development team manages the product’s versions. You can set up to five “levels” and set the separators between them. Proper versioning will help you to measure and manage quality improvements over time. Whenever a new build is created in the Applause platform, it will require you to name the build according to this format.
Note: If your development team does not “number” their builds, you may want to consider setting the format as “YYYY / MM / DD” to represent the testing date in a sortable manner.
Define the stages in your product development life cycle where you may be utilizing Applause for testing. For each Development Stage, select the appropriate values for:
Stage Label - Use the terminology used by your product team utilizing Applause for testing
Life Cycle Phase - Select the proper phase in the SDLC (Development, Alpha, Beta, Release Candidate, Release, Other)
Deployment Environment - Select the environment the software will be deployed on (Development, Integration, Testing, Staging, Production, Other)
Availability to end users - Select the scope of rollout to your install base (Pre-Release, Canary Release, Limited Release, General Availability, Other)
Once set, every time testing will be initiated for the product, you’ll be asked to select the Development Stage. Such contextual information allows us to better understand the severity and value of the issues, learn your patterns for fixing found issues and to tell you how your product is doing compared to other products.
Once done, click “Next” to continue.
In the Integrations section, you can assign already-set integrations between the Applause platform and your Bug Tracking System (BTS) and Test Case Management (TCM) systems. We will learn about how to integrate with Bug Tracking Systems later.
The integration will allow you to streamline your process with Applause by exporting the issues found during testing to your BTS, and syncing changes made to those issues in your BTS. Learn more about how to integrate with Bug Tracking Systems here.
To complete the Integrations step, select all integration connectors already set under your company that would be used by the product. If multiple connectors are selected, define one of them as default. The default connector will be used for automatic export (after bug approval), as well as pre-selected for the users doing the export.
Once done, click Next to continue.
Components are a feature in the Applause platform that allows you to set a custom list of different product components that testers can then select when they submit bugs. Components will help you identify the portions of your application that are giving testers the most trouble and require extra attention from developers.
Click the “Add an App Component +” button.
Select “Finish” when you have completed your entries.
Add the components that correspond to an area of your application, such as:
When setting up a test cycle, app components can be listed as focus areas in the cycle scope. This helps testers to concentrate their testing efforts on the appropriate areas of your application.
When submitting a bug, testers will select the most appropriate app component. For example, if they encounter a crash when attempting to checkout, they would select the “Checkout” component. The component associated with each bug is visible in issues.
Once your product is set up, you may edit it to apply updates. You can do this from the Products page or from the Product Details page itself.
- While on the Product list page, locate the product you want to edit.
- Click the Actions dropdown menu and select “Edit”.
Click the product name.
Select “Product Details” in the left navigation bar.
Click the Actions dropdown menu and select “Edit”.