Guiding principles for automated software testing [translate]

In a recent conversation with software testers, I kept hearing the same thing: Test automation is needed in most projects. Proper use of the following guidelines can help automate the testing process.

guiding principle 1: Avoid premature development of test scripts

We encourage software testers to conduct automated testing in the early stages of application development. However, in the case of the program is not complete, writing automated test scripts, the effect will be greatly compromised. You will have to rewrite your script at any time if you are writing a test script without changing the program. However, we do not recommend waiting until the entire program is stable to supplement the test script, the better way is to review the entire program, for the program's more complete functionality to write automated test scripts. (Note: Do not confuse with TDD here.)

guiding Principle 2: Reasonable planning test time

In order to release the software faster, if testers are always asked when to complete the test, they will eventually lose the credibility of the testing department. Automated testing can save you time, but we need to set aside time to solve unexpected problems, such as a script problem, and so on. These problems can happen at any time.

guiding principle 3: Test scripts focus on design changes

Testers are generally focused on writing test scripts for new software features, but they tend to overlook some of the already functional design changes. For example, a new version of the software provides users with a more efficient way to modify their passwords. In the previous version of the change password background color is red, and the new version of the modified in order to green, the general script is not to check whether the red background has been turned green, this is we need to modify the script to ensure that the background color changes.

guiding principle 4: Let the developer help modify the test script

The common problem with most testers is that scripting is not good enough to meet project needs, but this is exactly the strength of the development team. While in many cases the interaction between development and testers is not smooth, testers still have to try to get help. For example, once, writing a test script needs to use the Java,philips to ask the developer how to write a test script, she knows some Java, but there are a lot of knowledge points are not too clear. She found the relevant developers, worked with them to debug the software, and eventually the developer pointed out the cause of her scripting error. More importantly, they have established a more friendly relationship. Today, the developer uses her script for unit testing.

guiding Principle 5: Understanding Automation Testing

We need to understand why manual testing is needed at the same time as automated testing, and we need to measure the time and money saved by automated testing. Understand the purpose of automated testing and combine automated testing with manual testing to maximize profitability. (The last one made some changes, the original content, you can see the original content)

English Original: Original link

Reprint Please specify: Http://blog.csdn.net/sogouauto

Explore test art, Exchange test technology, Welcome to the "Sogou test"

Guiding principles for automated software testing [translate]