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

I recently read an article on infoq that discusses test automation. Although I am a development engineer

I still want to talk about the test.

1. Division of testing

In terms of the division of testing, I think it can be divided into technical testing and business testing, each of which has its own advantages.

From the current situation of the company, or the distribution of domestic tests, it is more business testing. But from the company

From the point of view of the development plan of the test, more and more attention is paid to the cognitive level of the test in terms of technology. Understand the origin of technology implementation

Reason, at the same time know how to test skills in the test, play a role in the work, is indeed quite large.

Personally, I think that the requirement of mandatory testing technical ability is not very reasonable. Need to be specific to the company

Technology, business scenarios; personal technology, test characteristics, comprehensive consideration.

Business testing is through the continuous accumulation of business knowledge, testing skills, for business models

Fixed products are indispensable for this kind of testing, but on the other hand, products with fixed business models

It should also be able to automate testing very well.

Technical testing, the ability to master the technology, can make the test in more details. Technical testing can be compared.

Testing is done in a simple and effective way, which is often efficient. For companies that are technologically complex to slightly higher, than

For example, Internet companies, companies with high requirements for stability, companies with high quality requirements, know how to test technology.

To be able to pay more attention to business processes and business implementations.

two。 Test automation

Test automation is not just the automation of test completion. Why do you say so? I have also experienced the company.

Test automation, the overall feeling that automated testing is still very difficult. Automation that can be used is always easy to achieve and easy to use.

It is always difficult to automate. Personally, I think it is necessary to achieve automation:

Automation that cannot be separated from actual business scenarios requires automated planning from the entire life cycle of the software. Automation needs to be continuous and lifecycle.

3.TDD

Some people are trying this, and some are making themselves miserable. The granularity of TDD must not be too small, for a

TDD with classes or small function points is impractical and time-consuming. The use of TDD must be in the process of comparison.

Business function points or business processes.

4. Integration test, unit test

Without talking about the concept, there are many articles on how to write a good unit test. We guarantee the quality of unit testing.

An important method of certification, of course, is based on well-written unit tests.

Personally, unit testing should be carried out on the basic modules and complex implementation function points. And in the business

For the above tests in the programming of the process, do not use unit tests.

Individuals are more inclined to use integration testing, which needs to plan test cases at a better height.

And management, only in this way can our tests be effective, sustainable and viable.

Do not cover for the sake of coverage, so the development is very difficult, and the more important tests are not effective; but good

Testing, you can reverse the analysis of code through coverage: that code is more, which code can be refactored, and so on.

Let's just think of that for a while.

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.