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

A brief Analysis of the misunderstanding of "Automated testing"

Many people think that "automated testing" is a test method that automatically executes and automatically analyzes whether the program is correct or not. Let's see if this is the case.

Let's do it.

Take the search interface of www.baidu.com as an example to test the correctness of the page Layout:

1. Page elements (whether the elements are complete, the location is correct, the text is correct, the hyperlink is correct, the multimedia is correct)

two。 Page display (whether the style is correct, zoom form adaptive, browser adaptive)

3. Script compatibility

For such a simple design, in order to achieve fully "automated testing", only what is required to enumerate the elements of the above checkpoints (use case design,

The workload of script development and code review is considerable, and the maintenance cost of this huge script is even more difficult to estimate. Since the implementation of "automated testing" is so complex, is it necessary to promote it?

The answer is yes. Because the only reason for the above dilemma is that we ignore the premise that "automated testing" is established:

1. Support for tools

two。 The input of manpower and time cost

3. The technical ability of the input personnel

4. Completeness of test cases and test data

5. Independence and correctness of Environmental deployment

6. Test the maintainability, reusability and correctness of the code

So when

1. Frequent program updates

two。 High degree of program coupling

3. High priority of program

The functions of different modules, different scenarios and different priorities can be extracted from the basic business logic to form the so-called general use case for automation.

In addition to routine testing of the system, various combinations can be arranged according to specific scenarios to meet the needs of the first round of smoke test for large projects.

To identify functional block

In addition, "automated testing" has many additional benefits, such as:

1. Test data construction

two。 Test data accumulation

(data accumulation in different scenarios can be reused and maintained in daily manual testing)

3. Basic function display

(it plays an intuitive role in showing that employees are familiar with the product.)

4. Wait

In addition to the "automated testing tools" QTP and Selenium, the commonly used testing aids include:

1. Excel: data statistics satisfying certain rules

2. SQL: data verification and restore

3. LoadTest: Web Test (checkpoint check for simple business) and LoadTest (correctness of concurrent processing)

4. UnitTest: White-box testing (including coverage statistics)

Analysis of "Unit Test"

Similarly, some people think that the implementation of unit testing is equivalent to the realization of the verification of all business scenarios of the unit function, which is also groundless. Because of

It is impossible to estimate how many sentences are needed to validate for one line of code.

Even if someone writes the so-called unit test code, who should guarantee the correctness of his test code? This constitutes an endless cycle.

So the real function of the common Unit Test is to ensure that when the data contract is certain, the function will not be block and output the result.

Meet the agreement, that's all.

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.