Exploratory testing & SBTM
Exploratory Testing
Exploratory testing is also known as ad hoc testing and was known solely by this term until the early 1990s when a group now called the “Context-Driven School” started using the term exploratory. Cem Kaner was the person that coined the term Exploratory Testing in his book “Testing Computer Software” and described it as:
“Simultaneous test design, test execution and learning with an emphasis on learning”
According to the different site, I found different definitions for exploratory testing-
In exploratory testing, testers do not work on the basis of previously created test cases. They check a system without a plan in mind in order to discover bugs that users may face when navigating a website or app without a specific aim or direction in mind.
Exploratory testing” – as the name suggests, is simultaneous learning, test design, and test execution process. We can say that in this testing test planning, analysis, design, and test execution, are all done together and instantly.
Exploratory testing is all about discovery, investigation, and learning. It emphasizes the personal freedom and responsibility of the individual tester. It is defined as a type of testing where Test cases are not created in advance but testers check the system on the fly. They may note down ideas about what to test before test execution. The focus of exploratory testing is more on testing as a “thinking” activity.
When using exploratory testing
Exploratory testing can be used extensively when the test team has experienced testers.
early iteration is required.
there is a critical application.
New testers into the team.
Session-Based Test Management
Set the goal and looking around that feature/ component/ functionality/ behavior or use case of the application, with the focus of finding defects. During this time, keep a note of your observations and report them at the end. This is called a Test Session and the pre-defined goal you set for your session is called a Test Charter. A test manager may then keep track of the number of test sessions allotted to a tester, their time spent, and their observations of value which may include defects, questions on design, or doubts about the usage of features.
Benefits of Exploratory testing
more bugs found
bugs are found earlier
more time spent testing, testing can start earlier
utilizes tester capabilities and promotes motivation testing team.
Using TestBuddy I have taken some notes
Comments
Post a Comment