Applause allows you to utilize our testing community not only for the initial reporting of bugs but also to run a re-test once a new build with fixes for those bugs is available, effectively verifying that you have fixed the discovered bugs.

Applause has fairly quick turnaround times for the fix verification and it can be initiated at any time via the Applause platform.

 

BFV from the Current Test Cycle

Utilizing an existing test cycle gives you and your TSM greater control and management capabilities in the BFV execution, including the ability to invite any tester with matching devices/environments to verify the bugs.

Benefits of BFV from the Current Test Cycle

• BFVs, test cases and exploratory testing can all be run within the same cycle using the same testers
• Requesting BFVs as part of a standard test cycle allows for iOS builds to be resigned

The BFV will be done using the same build as set for the current test cycle. To initiate a BFV follow the below steps:

1. Select a product.
2. Open Test Cycles from the left navigation bar and either copy or edit an existing test cycle.
3. Go to “Step 2: Scope” and scroll down to “Known Issues & BFV” under Testing Scope.
4. Click the “Edit Known Issues & BFV” button if you already have Known Issues in this cycle or click the “Add Known Issues & BFV” button.
5. A list of bugs and Known Issues available for the product is displayed. Select the fixed bugs you’d like to verify. The selected bugs are also checked to be added to your Known Issues list.
6. Click “Done” when all the bugs are selected. Remember to save the test cycle so your changes are implemented.
7. When a bug is added to BFV, a BFV-type test case is created and is made available to testers who are already in the cycle. Make sure to notify the Applause team so they can monitor the process for you.

 

How to Initiate BFV from a Bug Tracking System

The majority of our customers prefer to take the results of our test cycles (i.e. bugs) and export them to their native Bug Tracking Systems (BTS), such as Jira. This enables them to manage the subsequent work with their development teams in the system they are used to.

Customers implementing the Two-Way Jira Integration or Two-Way ADO Integration may also automatically indicate to the Applause platform the bugs which are ready for BFV based on the issue status in their BTS, as well as automatically get updated with the verification results into their BTS issue.

Read more on how to set up the Bug Verification Workflow using the 2-Way BTS Integration.

 

How to View BFV Progress and Results

Testers will view the BFV as if it was a “regular” test case and report back their findings in the form of a Pass or Fail.

Steps to View the BFV Progress and Results

1. Open the Test Cycle where the issue was reported or open the cross-cycle issues list from the left navigation bar.
2. From the issues list select the issue that you requested to verify and want to view its BFV progress and results.
3. View the current BFV status for the bug under Verification.
4. View details of each BFV run, including date executed, test cycle number, result and device/environment under Additional Information.

Note: By default, the global issues list will hide all closed test cycles. To show the issues in the closed test cycles, check the “Include Closed Test Cycles” box.