Summarize your view of automated testing

I. Why Automation?

1. Do regression testing, reduce the amount of manual : This avoids the repetition of the work of the testers, but also allows us to have more energy to do more meaningful things, but also can let us reduce some boring feeling.

2. Test manual testing is not possible or difficult to implement features : for example, to simulate 10 million HTTP concurrent requests, if it is manual testing, this is not possible.

3. To facilitate work, write a gadget :

For example, I am doing certain operations, I want to get the information I want from the background log in real time, but the background log information is too much, many are not what I want.

So that I can view the log, I could write a gadget that extracts what I want from the log in real time.

Two. When is the right time for automated testing?

1. Agile Project : If the project takes agile mode, because the iteration cycle is too short, the test can not return all the previous functions, so it is necessary to use the automated test to do regression testing.

2. When the system cycle is relatively long .

If the system cycle is too short, then the automated tests that have taken a long time to write may have been used for a short time or a limited number of times, so it is not worth it.

3. The project is relatively stable, the demand will not change too quickly .

The need to change too quickly can lead to automated tests that always fail. The cost of automating maintenance is too high, and even due to being too busy, testers have no time to maintain, resulting in previously written automation use cases being idle and wasting time.

Three. Cost of automated testing

1. Time Cost

A. Training cost: If you want to implement automation in a project, you will need to do some training (basic theory, programming language) in the prior period.

B. Writing costs

C. Maintenance Costs:

Maintaining an automated test environment is always available

New or modified bugs may cause some old function automation tests not to work (such as a new bug or a front-end automated test, the path of an element has changed, etc.)

2. Cost of Money : Some are not open-source automated testing tools or very expensive, such as QTP

Four. How to choose an automated test framework (tool)

The test framework is to encapsulate some common methods, which are convenient for us to use and reduce the duplication of code.

You can choose to write your own test framework, or you can choose some of the most commonly used automated testing frameworks.

Interface testing is more common: robot Framework,fitnesse

Unit Test: Junit,testng,nunit

Front page test: Selenium, Watir

Of course, many times we can also combine multiple test frameworks to use

Five. Disadvantages of automated testing

1. Cannot completely replace the manual test :

There are situations where automation is not possible (such as off-grid power outages), or the cost of writing automation is too high;

Automation scripts are inflexible, and some manual tests are obvious problems that are easy to ignore because they are not in the script's test scope;

What's more, automated testing is hard to find new bugs.

Therefore, automated testing is still not a complete replacement of manual testing, we can use it to assist the test, see the new function or after the bug modified, the original function can be normal operation.

2. High cost of writing and maintenance

Six. Testers in the automated testing process easy to fall into the misunderstanding

1. blindly pursue the coverage of automated testing , while ignoring the practical significance of automated testing.

Some of the functions of manual testing is simple, but to achieve automated testing is relatively difficult, time-consuming, cost-effective, some features may be just a temporary function, there is no need to write automation.

2. write automation for Automation , regardless of whether this is really helpful for our system testing or not considering whether our project is really suitable for automation.

3. No manual tests are required for automated tests

4. Automated testing can only be a regression test: In fact, automated testing can not only do regression testing, but also to deal with the data (such as the simulation of 10 million HTTP concurrent requests), or to do some small tools to assist the daily work

In addition: In fact, I feel that the key to doing a good job in automated testing is not to say how much you have in your technology, but whether your automated test cases cover the focus of those tests. So I think the key to automation is your automated test case design.

Summarize your view of automated testing