Course 4: Bug Fix Verification
Methods and instructions on running a bug fix verification.
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.
Utilizing an existing test cycle
Triggering an automatic creation of a standalone test cycle
With both methods available, Applause has fairly quick turnaround times for the fix verification and each can be initiated at any time via the Applause platform.
Utilizing an existing test cycle gives you and your TA/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.
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:
Open Test Cycles from the left navigation bar and either copy or edit an existing test cycle.
Go to “Step 2: Scope” and scroll down to “Known Issues & BFV” under Testing Scope.
Click the “Edit Known Issues & BFV” button if you already have Known Issues in this cycle or click the “Add Known Issues & BFV” button.
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.
Click “Done” when all the bugs are selected. Remember to save the test cycle so your changes are implemented.
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.
You can trigger the automatic creation of a standalone test cycle in which the original tester who submitted the bug will be assigned for the re-test, as well as a second tester with matching devices/environments. The Applause platform will automatically de-assign those testers if re-tests were not completed within 48 hours and assign others instead.
In certain cases, you may consider running the BFV as a standalone, dedicated test cycle managed automatically by the Applause platform. Such cases may include:
There is a need to specify a build for the BFV, which is different from the build used in the current test cycle
Matching the tester who originally reported the bug is significant, however, there is nothing to prevent other testers from participating in the verification
There is no need to run BFV next to exploratory or normal test cases
Click Test Cycles from the left navigation bar.
Open the Test Cycle and click the Issues tab.
Browse to the necessary issue.
Then click the Actions dropdown menu and select “Request Verification”.
The Fix Verification dialog box will open, which will allow you to specify a build to conduct the retest on. Type in any comment or further instruction in the comment field.
Click “Send” after you finish.
Note: You may save time by selecting multiple issues from the issues list (either within a test cycle or the global one) and click Ask for Verification as a bulk.
- The verification request will be picked up by an automatic process within 15 minutes, designed to create a standalone new BFV cycle every week to verify all the fixes requested during that week
- The standalone BFV test cycle will be managed automatically and will not be displayed under your Test Cycles list
- Once the cycle is created and the BFV is added to it, the original tester is invited to verify the fix, along with an additional (random) tester that meets the reported bug’s devices/environments
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 may also automatically indicate to the Applause platform the bugs which are ready for BFV based on the issue status in Jira, as well as automatically get updated with the verification results into their Jira issue.
Read more on how to set up the Bug Verification Workflow using the 2-Way Jira Integration.
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.
Open the Test Cycle where the issue was reported in or open the global issues list from the navigation bar under Test Cycles.
From the issues list select the issue that you requested to verify and want to view its BFV progress and results.
View the current BFV status for the bug under Verification.
View details of each BFV run, including date executed, test cycle number, result and device/environment under Additional Information.
Note: By default, the list will hide all closed test cycles. To show the issues in the closed test cycles, check the box “Include Closed Test Cycles”.