Why we need automated testing

Many teams have tried automated tests, but they are generally tasted, and few non-pure technical teams can continue on the road to automated testing.

Automated Testing is a broad concept, in general, all the alternatives to manual testing are automated tests, and we generally say unit testing is a kind of automated testing, unit testing many people call "millisecond-level automated testing."

Automated testing is difficult and, in a sense, more difficult than performance testing. Performance testing can rely on a lot of things, such as LR, and automated testing tools in many cases just a semi-finished, such as selenium webdriver, you need to spend a lot of time to write use cases, and maintain these use cases, this process is long and difficult, Especially for some non-development experience of the test students, the process is very painful, the daily work content seems to be self-abuse, and self-abuse after a period of time confidence basically collapsed, from this talk about automatic color change, so the fault is due to automated testing strategy and technology, and not from itself to find problems.

But practitioners of automated testing tend to be luckier than performance tests. The simplest example is that the average performance tester leaves the tool largely inactive, while the automated testers can use their own language knowledge and code knowledge to create their own tools, and to be honest, this is a very fulfilling thing, from simple CLI tools to complex web tools, Everything is a blessing before the automation test practice.

automated testing is difficult, so why should we insist on automation?

Unit testing is the most basic and fundamental way to ensure the quality of code, unit testing is a kind of automated testing, so the importance of automation is self-evident;

Integration testing is well suited to use automated means in many cases, the most obvious example being the integration test in rails;

When your unit tests and integration tests are not done, and even if you do not, the UI-level automated tests can play the role of firefighters, despite their high cost, maintainable UI test code is the Gospel of regression testing and an important means of improving test productivity;

Automated testing can develop a team, if a team can be automated testing, then their development level must be not low, and if these people to do development, the quality of the code is rather higher than the average developer, the reason is easy to understand, testers believe that what has not been tested is not credible, If the code is not tested, then the code is inherently untrustworthy, and untrusted code needs to be overwritten with unit tests, so this can fundamentally improve the quality of the code.

Do third-party testing must have automated testing, such as the domestic relatively good such as Testin, testbird, foreign words testdroid,perfectomobile, etc.

Transferred from:http://www.easonhan.info/2013/12/06/why-automation/

Why we need automated testing