开发自动化测试脚本的技巧和心得（Develop skills and tips for automated test scripts）.docVIP

开发自动化测试脚本的技巧和心得（Develop skills and tips for automated test scripts） The authors describe some of the techniques for building more maintainable and robust automated test scripts in this article. The authors provide valuable insight to testers who use automated test tools and build automated test scripts for future testing. This article provides a lot of advice on documenting test scripts, debugging test scripts, performing peer review and synchronization test scripts for test scripts. Incremental debug script Recording test scripts, like any other software development effort, can become very large. To successfully play back, you need to debug hundreds of lines of code, and for parameterized data-driven test scripts, it may contain several data sets. The common debugging test script method is to first record all business processes and requirements, and then the tester replays the test script to verify and correct the problem. The tester continues debugging the script until it is successfully replayed with a (or more) set of data sets. When the test script has hundreds of lines of code, the verification point, branch of logic, error handling, parameters and data in a number of recorded the correlation between business process, debugging and solve the problem of the test scripts become special boring and hard to handle. For debugging complex and lengthy test script, to a more manageable approach is part of the script and recording in the recording before the rest of the test script debugging them separately. After testing a single part, you can determine how part of the test script works and how the data flows from one recorded process to another. After all parts of the test script are recorded, the tester can play back the entire test script and ensure that the script is correctly played back from beginning to end with the same or more data sets. For example, I recorded and automated a complex test script that performed the following business processes: Check the inve