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

Get to know Bug and explore public testing

With the rapid development of mobile Internet services, more and more people realize the importance of Bug to explore public testing. So what is the Bug exploration public test? Bug exploratory mass testing was proposed by testing expert Dr. Cem Kaner in 1983. Bug exploratory mass testing is a software testing style, which emphasizes the individual freedom and responsibility of independent testers. In order to continuously optimize the value of their work, test-related learning, test design, test execution and test result analysis are implemented in parallel throughout the project. The definition includes three aspects:

A way of thinking

Bug exploration public testing emphasizes the selection of appropriate testing methods according to the current environment, rather than limited to specific testing techniques. Testers can use any of the testing techniques in exploratory testing, or they can apply exploratory style to any testing activity.

A kind of responsibility

Bug explorers should be responsible for individuals and teams, mobilizing all energy and giving full play to human flexibility.

Cyclic iteration

The purpose of Bug Exploration testing is to quickly iterate test learning, test design, test execution and test result analysis as a cycle to continuously collect feedback, adjust tests, and optimize value.

Bug explores the value of mass testing

Shortcomings of conventional testing methods

Conventional testing methods can effectively ensure that there are no major problems in the single or multiple common scenarios set by testers, but the environment of users is very different from that of APP developers, such as completely different network environments (2G, 3G, 4G, WIFI), inconsistent operators (telecom, mobile, Unicom), completely different mobile devices and OS systems, and so on. Traditional testing can not cover all possibilities and scenarios, which is the root cause of many products with excellent design but still poor reviews. At this time, the mobile application Bug to explore public testing is particularly important and necessary.

Bug explores the application of mass testing in different enterprises

There are different ways to use Bug to explore public testing in different enterprises. In large enterprises (banks, insurance, securities, government, listed companies, etc.), there are a large number of internal employees, each employee has 1-2 personal mobile devices, this natural advantage provides abundant resources for internal public testing, large enterprises can "stay at home" to complete the Bug exploration public testing of mobile applications relying on the sound public testing information management platform. On the other hand, small and medium-sized enterprises (entrepreneurial Internet companies, information departments that cannot mobilize more internal resources, etc.) do not have the advantage of abundant available resources. This kind of enterprises obviously need the support of external forces to carry out Bug exploration public testing. They can choose a mature and reputable public testing platform, and the external public testing platform can provide testing expert resources to complete the corresponding Bug exploration public testing.

Conventional testing and Bug Exploration Public testing

Conventional testing is an important means to ensure the quality of testing. Bug explores that mass testing can effectively supplement differentiated testing contents such as scenarios that can not be covered by conventional testing and a variety of user behaviors. The two combine and complement each other, and one of them is indispensable.

Bug explores the significance and function of public testing

The most important feature of exploration testing is to create new and different testing ideas and methods while testing the test objects. This is very different from the strict "design first, then execute" in the traditional software testing process.

Exploratory testing emphasizes that there should be more divergent thinking in the testing process, which is the biggest difference from conservative testing. Conservative testing emphasizes the assumption of perfect test cases, and testers execute tests strictly according to test cases, which more or less limits testers' test thinking, and testers often lack subjective initiative.

Exploring testing makes the testing work away from conventional use cases, and deeply excavates the Bug which is not easy to be found in the application, so as to ensure the stability of product quality and improve the product experience.

Many people verify the core functions in a large area, and through divergent testing, simulate a variety of abnormal scenarios and extreme testing methods to find out all kinds of potential problems and risks.

Bug explores public testing to simulate real users, combined with team testing experience, to maximize user habits and paths, to explore complex operation processes, to truly simulate abnormal application scenarios and system-specific features, to ensure smooth use of major functions, to avoid problems affecting user experience, and to discover Bug that is difficult for developers to find.

Mobile application Bug to explore the process of public testing

Test environment preparation

The Bug exploration and public testing of mobile applications is usually carried out in the external network environment. You can choose the SIT environment, UAT environment, grayscale release environment and production environment with security protection. In particular, it should be pointed out that confidential aspects such as information security protection and intellectual property protection should be avoided as far as possible, as public testing may be carried out outside this organization. The reinforcement of the APP installation package is also a very important link. Usually, the test package in the research and development process is not reinforced.

Bug needs a relatively stable environment to explore public testing. If the test environment used for this task is integrated and released many times every day, it will affect the effectiveness of public testing. It is possible to propose many invalid defects related to environmental problems, or lead to test interruption, and the tester's mood is seriously frustrated, so that the testing effect is greatly reduced.

Test design

There are usually two modes of Bug exploration: scene-based exploration or freestyle exploration. Obviously, the scene-based Bug exploration public test is more targeted, both the focus of the problem and the quality of Bug are far better than the free-style exploration public test.

The public test based on the scene does not need to give a very detailed Test Case (Step By Step mode). Although the detailed testing steps are very clear, it will greatly limit the tester's thinking. Based on the testing of the scene, we only need to give clear goals, such as: 1, complete registration 2, complete commodity selection 3, complete order payment and other test contents, so that testers can explore the Bug existing in the execution process based on the goal.

Organization and execution of tests

The Bug Discovery Test usually ends in a very short time after the task is released, and the task without cycle usually ends within 24 hours. Within 24 hours, you not only need to wait for feedback from the test results, but also need to solve the various questions raised by the participants. The people who participate in the public test of Bug exploration are generally testers other than this Team, and may have some doubts about the first use of the product. This is normal, perhaps you can find the problem of product design from their questions, because 2C mobile applications do not need any operation manual, if the user is difficult to get started, this is a serious experience problem. How to deal with the testers' questions and problems needs to be solved by a sound public testing information management platform, either through IM or through announcement management.

Test result confirmation

Test result confirmation, the main work is the confirmation of test execution process and the confirmation of Bug. The confirmation of the test execution process means that the tester has indeed completed the whole Bug exploration testing process according to the given scenario, usually based on screenshots, videos and so on. Bug confirmation is the focus of test result confirmation, including: effective Bug identification, invalid Bug identification, duplicate Bug identification, Bug that needs to be reproduced further, etc. This is a bit of a workload, and it looks complicated, but if you use the ability to automatically identify duplicate Bug, it will make duplicate Bug recognition intelligent and efficient. At present, many enterprises are using QQ group, WeChat group and other ways to manage public testing, which obviously can not achieve the purpose of efficient management of public testing.

Bug Exploration Public Test report

The Bug Exploration Public Test report is a summary of the whole testing activity, including: the cost of public testing time, the cost of public testing, the analysis of the coverage of public testing, the Bug analysis of public testing findings, and the risk analysis that the data of public testing can measure. With the application of platform management, the above contents can be output automatically, and there is no need to re-collect data artificially.

Bug, based on the shared economy model, explores the mass testing model, which makes testing everything more efficient, and provides a very good way for agile iteration.

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.