Shulou(Shulou.com)06/03 Report--

Exploratory testing is a freewheeling style of software testing that emphasizes the simultaneous development of test learning, test design, test execution, and test result evaluation activities to continuously optimize testing efforts. Given its improvisation, rapid experimentation, and dynamic adjustments, its way of thinking dates back to the earliest years of software development.

Exploratory testing is rich in content. The following text defines the core of exploratory testing.

Exploratory testing is a style of software testing that emphasizes the individual freedom and responsibility of independent testers, and in order to continuously optimize the value of their work, test-related learning, test design, test execution, and test result analysis are performed in parallel throughout the project as mutually supportive activities.

The definition could be discussed in three parts.

Firstly, exploratory testing is a software testing style, not a specific software testing technology (such as equivalence class division, boundary value analysis, etc.). As a thinking method, exploratory testing emphasizes the selection of appropriate testing techniques according to the current context, rather than being limited to specific testing techniques. Testers can use any testing technique in exploratory testing and can apply exploratory testing to any testing phase.

Under the guidance of this testing style, a number of testing techniques have emerged to support exploratory testing. For example, James A.Whittaker proposed a set of "wandering testing" techniques based on systematic false guessing and testing metaphors in Exploratory Software Testing, which enriched the means of exploratory testing. Jonathan Bach and James Bach, for example, invented Session-Based Test Management, which significantly improved exploratory testing in terms of test organization, reporting, communication, and measurement. For example, the development tool Microsoft Visual Studio 2010 began to support manual testing and exploratory bugs (Exploratory Bug), although the related functions are slightly thin, but it reflects the software industry's recognition of exploratory testing, can not indicate that exploratory testing aids and automation will get more attention and development.

Therefore,"exploratory testing" should have two meanings.

First. Connotation is a kind of software testing style and thinking method, which does not stick to specific testing technology.

Second. Its extension is a group of test technologies developed under the guidance of this thinking method, including test design methods, test management methods, test auxiliary tools, etc.

Exploratory testing emphasizes the freedom and responsibility of independent testers. The tester should be accountable to the individual and the team, mobilizing all energy, utilizing human flexibility, and continuously optimizing individual and team output as a whole. Testers are knowledge workers in software enterprises. Management guru Peter Drucker argued that knowledge workers must manage themselves. On the one hand, he recommends that knowledge workers set their own work goals (to do the most valuable work at the moment according to the project situation) and optimize their productivity and output quality through continuous innovation, continuous learning and continuous communication. On the other hand, he advised companies to trust employees, empower them and invest in them as assets. These two aspects can be viewed as potential requirements of exploratory testing for employees and businesses.

Exploratory testing suggests that test-related learning, test design, test execution, and test result analysis be performed in parallel as mutually supportive activities throughout the project. In fact, the human brain has difficulty performing multiple tasks in parallel. Exploratory testing is designed to iterate rapidly through test learning, test design, test execution, and test result analysis as a cycle to continuously collect feedback, adjust tests, and optimize value.

Test learning: learn anything that can guide testing, including industry background, domain knowledge, technology platforms, test techniques, product defects, project risks, etc.

Test design: arranging test plans, developing test strategies, developing test ideas, and producing test support materials

Test execution: Executes tests and collects results. Tests can be performed manually or automatically.

Analysis of test results: Analyze and interpret knowledge learned from testing. Possible activities include determining whether the test passed, understanding the product implementation, identifying risk areas, and evaluating whether the test method was effective.

Exhaustive testing is not feasible in real-world software projects. Any test is a sampling test, and there is a risk that test resources will be invested and defects will not be found. As the project evolves, so does the risk of testing. Exploratory testers collect and interpret test intelligence over the course of a project, optimize test decisions and designs, and apply them immediately to test execution, analyzing test results to assess development status and test risks. Such cycles help maximize the value of testing and reduce the risk of software projects.

Excerpt from "The Road to Exploratory Testing Practice"---Shi Liang Gao Xiang

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.