How can I do test automation (TA)?

in the introduction and application of automated testing, we understand some basic principles:

-Choose good tools, the most popular tools may not be suitable for their own, the real tool is the best for their own. such as robot is not necessarily the best, but its multi-machine interactive collaboration capability is not the other tool

-Select different test tools based on different features of the client, Web, and server, such as Web links, fast UI changes, and complex logic, tools that are robust, stable, and adaptable to different platforms (Windows, Linux, Mac OS) and browsers (IE, Forefox, NS, ...)。 The server generally does not have a UI interface, mainly for the support of different protocols.

-Load, performance automation testing is easier to implement, but functional testing is more difficult

-Software test automation (TA), although it has many advantages, but only a manual test of a supplement, TA can not replace manual testing. In the system function logic test, acceptance test, applicability test, involving physical interaction test, use the manual test method of black box test, Unit test, integration test, system load or performance, stability, reliability test are more suitable for TA.

-the tool itself does not have the imagination and the flexibility, the automatic test can only discover the 15-30% flaw, but the manual test may discover the 70-85% flaw, the TA tool carries on the function test, its accurate meaning is the regression test tool, because the tool cannot discover many new problems, But you can guarantee the accuracy and objectivity of testing the parts that have been tested.

-Find the test automation of the entry point, generally from the long-term beginning of new products, synchronization, and select some relatively easy to automate the processing, manual testing more complex modules, such as a large number of API calls, mail template processing, etc.

-Incorporating test development into the entire software development system is necessary, the system is not testable, and no good tools are available. and test automation upfront investment, so that the software development of the early allocation of more time, the test execution time can be shorter; Manpower distribution is also different, the rational scheduling of resources.

-Test automation relies on test processes and test cases. Without a good test flow or a design-effective test case, the test tools will be less efficient.
Large investment in software testing automation

But there is one problem that bothers us, namely, which of the following models is better.

1. Specialized TA Team, responsible for the development of automation modules, after the development of the team to carry out functional testing. Artificial increase of a handover work, communication level, but the TA team full heart scipting, development efficiency, and is conducive to retaining TA engineer

2. Part of the product module contracted to the TA team, TA development well, they hand-tested less, let TA team themselves drive, the effect should be good, but the development efficiency may be low, or TA team feel too much pressure, or do not like manual testing, easy to be forced to go to do development.

You are welcome to comment.