【Reprint】Five misunderstandings of software testing

 

 

    One of the misunderstandings: software testing after software development is completed

 

  It is generally believed that a software project goes through the following stages: requirements analysis, outline design, detailed design, software coding, software testing, and software release. Accordingly, it is considered that software testing is only a process after software coding. This is the wrong perception of not understanding the software testing cycle.

Software testing is a series of process activities, including software testing requirements analysis, test plan design, test case design, and test execution. Therefore, software testing runs through the entire life process of a software project. In each stage of the software project, testing activities with different purposes and contents should be carried out to ensure the correctness of each stage. The object of software testing is not only software code, but also software requirements documents and design documents. Software development and software testing should be interactive, for example, unit coding requires unit testing, and module assembly requires integration testing. If you wait until the software coding is completed before testing, then the testing time will be very short, the testing coverage will be very incomplete, and the testing effect will be greatly reduced. What's more serious is that if errors in the software requirements phase or outline design phase are found at this time, it will take a lot of time and manpower to fix such errors.

 

Misunderstanding 2: If quality problems are found after the software is released, it is the fault of the software testers

 

This realization discourages software testers. Errors in software may come from various processes in a software project. Software testing can only confirm that the software has errors, but cannot guarantee that the software is error-free, because fundamentally speaking, it is impossible for software testing to find all errors. From the perspective of software development, the high quality of software is not measured by software testers, but is designed in various processes of the software life cycle. The occurrence of software errors cannot simply be attributed to the responsibility of one individual. Some errors may not be caused by technical reasons, but may come from chaotic project management. The various processes of the software project should be analyzed, and the reasons for errors and improvement measures should be found from the process improvement aspect.

 

Misunderstanding 3: Software testing requirements are not high, just find as many people as you like

 

Many people think of software testing as the work of installing and running programs, clicking the mouse, and pressing the keyboard. This is caused by not knowing the specific techniques and methods of software testing. With the development of software engineering and the improvement of software project management experience, software testing has formed an independent technical discipline and evolved into an industry with huge market demand. Software testing technology is constantly updated and improved, new tools, new processes, and new test design methods are constantly being updated, which requires mastering and learning a lot of testing knowledge. So, a programmer with programming experience is not necessarily a good test engineer. Software testing includes two aspects: testing technology and management. To master these two aspects completely requires a lot of practical experience in testing and the spirit of continuous learning.

 

Misunderstanding No. 4: Software testing is for testers, not for programmers

 

  Development and testing are complementary processes that require software testers, programmers, and system analysts to maintain close contact, and require more communication and coordination in order to improve testing efficiency. In addition, the unit testing should mainly be done by programmers, and testers can help design test cases if necessary. For software bugs found during testing, many require programmers to fix them by modifying the code. Programmers can purposefully analyze the type and quantity of software errors to find out the location and cause of errors, so as to avoid the same errors in future programming, accumulate programming experience, and improve programming ability.

 

Misunderstanding No. 5: Do less testing when the project schedule is tight, and do more testing when time is affluent

 

This is the performance of not paying attention to software testing, and it is also the performance of software project process management confusion, which will inevitably reduce the quality of software testing. The smooth realization of a software project requires a reasonable project schedule, including a reasonable test plan. Risk analysis and corresponding countermeasures are required for any problems in the process of project implementation. Do not simply shorten the development schedule because of the delay. Test time, manpower and resources. Because of the incomplete testing brought about by shortening the testing time, the potential risks caused by the decline of project quality often result in greater waste. The best way to overcome this phenomenon is to strengthen the planning and control of software processes, including software test planning, test design, test execution, test measurement and test control .

 

TestBird , an automated testing platform , initially started from mobile game testing, and has accumulated a high reputation in the mobile game circle. It has also entered the field of APP testing. At the same time, TestBird has also joined the field of smart hardware testing. Not only that, TestBird has also established three test platforms of cloud mobile phone, cloud test and cloud analysis. Through self-service App function test , remote real machine debugging, real machine compatibility test, real person experience test, real person stress test and crash analysis and other products, Provide one-stop quality management services for mobile applications from R&D to launch to operation, help mobile application companies to establish a complete quality management system, and comprehensively improve the DAU , retention rate and payment of mobile applications.

 

 

From: China Test Platform

Guess you like

Origin http://10.200.1.11:23101/article/api/json?id=326582251&siteId=291194637