Exploratory Test Practice 1

Recently, I tried to apply exploratory testing to my daily work. Below are some of my experiences.

First, I will find a piece of paper and a pen, and list the functional points to be tested one by one. Then I will find the bug fix that affects these feature points from the bug fix in the recent period, for example, two weeks. From the comment or release note of the Bug fix given by Dev, tryCodeTo understand how Dev fixes the bug and the possible impact of fixing the bug. Based on the above information, enrich and improve each function point to test the content to form a test outline. Next, perform the test based on the test outline. Some feedback will be received during the test. For example, based on the feedback, you may know which content in test outline needs to be further expanded, and which content does not need to be tested for more time. Use these feedback to correct the previous test outline, and then perform further tests based on the modified test outline.

The exploratory test gives me the feeling that QA should constantly correct the test case or test outline according to the information obtained during the test, perform further tests based on the new test cases or test outline. In the exploratory testing process, each iteration will bring QA closer to the bug to be searched. I usually control the entire Exploratory Test process within 4-6 hours.