Open Category List

Product Components

4 minutesread

Using Product Components

As you are setting up your product in the Applause Platform, you will be able to define the components of your product. Components are essentially screens, functionalities,  workflows or other distinguishable areas within your product you would like to name out. Product Components are then used in the following manners:

  • Testing Scope: You will be able to define which Product Components are to be tested in a specific test cycle, focusing our testing community in the areas relevant to you and reducing Out-of-Scope issues. Learn more about test cycle creation here.
  • Results Context: Testers will be required to mark the issues they are reporting with the appropriate Product Component. Your testing results, thus, will instantly reflect your weak spots within your digital product. Learn more about test results breakdown by components in the Activity Dashboard here.
  • Resource Allocation: Once you are able to identify areas with quality issues, you are able to make better data-driven decisions on your strategy, including where to spend time testing more, what areas may require extra attention from developers, and so on.

Identifying your Product’s Components

While some development organizations have a clear vision of the components their products should be represented by, others may need to invest the time to identify those. You are welcome to collaborate with your Applause Team to find the solution that works best for you.

Some few common examples for Product Components may be:

  • Functional (for instance: Registration, Login, Search, Cart, Checkout).
  • User Experience (for instance: Searching, Evaluating, Paying, Returning).
  • Localization (for instance, English, Spanish, French)

Please note that it is not recommended to represent your development stage (Stage, Production), environments (Windows, Linux), testing type (Structured, Exploratory) or issue types (Functional, Localization) as Product Components. All of those are handled using other standard fields in the Applause Platform.

 

Setting Up Product Components

To setup your Product Components, follow the below steps:

1. While in the New / Edit Product Wizard, navigate to step 3, Components. Learn more about adding new products or editing existing ones here.

2. Click on Add an App Component. 

3. The Add App Component dialog box opens. Type in the Component name and description.

4. Once done, click Done to add the component to the Components step.

5. Once all components are added, click Save & Close to save the updated product settings.

SubComponents

For some of your Product Components you may need to add a second hierarchical level of component distinction. The Applause Platform allows you to easily set subcomponents for this purpose.

To add subcomponents, follow these steps:

1. While in the New / Edit Product Wizard, navigate to step 3, Components.

2. Make sure the product already have the top-level components set up and saved.

3. Click the Actions button next to the top-level component, and select Add SubComponent.

 

4. The Add App Component dialog box opens. Type in the Component name and description.

5. Once done, click Done to add the subcomponent to the Components step.

6. Once all subcomponents are added, click Save & Close to save the updated product settings.

Managing Components and SubComponents

Once the Product Components and SubComponents are set, you are able to manage them. To manage your components and subcomponents, follow the below steps:

1. While in the New / Edit Product Wizard, navigate to step 3, Components.

2. Click the Actions button next to the top-level component, and select any of these options:

  • Edit: Note that any changes made will all current and past test cycles and issues. In case this is not desired, consider archiving the component and create a new one instead of it.
  • Move Up / Down: Control the sort order the components will be displayed for the testers when reporting issues.
  • Move to a New Component (for subcomponents only): In case a subcomponent was accidentally created under the wrong component, you’ll be able to move it using this option.
  • Archive: Remove the component from any future test cycle and issue report – but keep it for past ones for reporting purposes.
  • Delete: Remove the component without keeping historical data about it (use with care). Note that the component will be deleted only after you click Close & Save to save the updated product settings. You are able to undo the deletion until then.

0
0
515
4 minutesread

Related Knowledge Base Posts