| Description |
1 online resource |
|
text file |
|
PDF |
| Summary |
Quickly access 50 tips for software test engineers using automated methods. The tips point to practices that save time and increase the accuracy and reliability of automated test techniques. Techniques that play well during demos of testing tools often are not the optimal techniques to apply on a running project. This book highlights those differences, helping you apply techniques that are repeatable and callable in professionally run software development projects. Emphasis is placed on creating tests that, while automated, are easily adapted as the software under construction evolves toward its final form. Techniques in the book are arranged into five categories: scripting, testing, the environment, running and logging of tests, and reviewing of the results. Every automation engineer sooner or later will face similar issues to the ones covered in these categories, and you will benefit from the simple and clear answers provided in this book. While the focus of the book is on the use of automated tools, the tips are not specific to any one vendor solution. The tips cover general issues that are faced no matter the specific tool, and are broadly applicable, often even to manual testing efforts. What You'll Learn: Employ best-practices in automated test design Write test scripts that will easily be understood by others Choose the proper environment for running automated tests Avoid techniques that demo well, but do not scale in practice Manage tests effectively, including testing of test scripts themselves Know when to go beyond automation to employ manual methods instead. |
| Bibliography |
Includes bibliographical references and index. |
| Contents |
At a Glance -- Contents -- About the Author -- About the Technical Reviewers -- Introduction -- Chapter 1: Scripting -- 1-1. Do Not Use Record & Play in Real Projects -- 1-2. Do Not Use Pauses -- 1-3. Provide Exit by Timeout for Loops -- 1-4. Do Not Consider Test Automation as Full-Fledged Development -- 1-5. Do Not Write Bulky Code -- 1-6. Verify All Options of Logical Conditions -- 1-7. Use Coding Standards -- 1-8. Use Static Code Analyzers -- 1-9. Add an Element of Randomness to Scripts |
|
1-10. Do Not Perform Blind Clicks Against Nonstandard Controls1-11. Learn and Use Standard Libraries -- 1-12. Avoid Copy and Paste -- 1-13. Do Not Use tryâ#x80;Œcatch with an Empty catch Block -- 1-14. Separate Code from Data -- 1-15. Learn How to Debug -- 1-16. Do Not Write Code for the Future -- 1-17. Leave the Code Better Than It Was -- 1-18. Choose a Proper Language for GUI Tests -- 1-19. Remember to Declare and Initialize Variables -- Chapter 2: Testing -- 2-1. Do Not Duplicate Tested Application Functionality in the Scripts |
|
2-2. Each Test Should Be Independent2-3. What Should Not Be Automated? -- 2-4. Ask the Developers for Help -- 2-5. Cloud Testing -- 2-6. Introduce Automation for Corner Cases -- 2-7. The Difference Between Error and Warning -- 2-8. Use the Appropriate Methodologies -- 2-9. Verification of Individual Bugs -- 2-10. Make a Pilot Project Before Writing Real Tests -- Chapter 3: Environment -- 3-1. Choose a Proper Set of Tools for Your Needs -- 3-2. Do Not Automatically Register Bugs from Scripts |
|
3-3. Do Not Chase After a â#x80;Green Buildâ#x80;#x9D; in the Prejudice of Quality3-4. Learn the Tool You Work With -- 3-5. Make Use of Version Control Systems -- 3-6. Avoid Custom Forms -- 3-7. Simplify Everything You Can -- 3-8. Automate Any Routine -- Chapter 4: Running, Logging, Verifying -- 4-1. Run Scripts as Often as Possible -- 4-2. Perform an Automatic Restart of Failed Tests -- 4-3. A Disabled Test Should Be Provided with a Comment -- 4-4. Errors in Logs Should Be Informative -- 4-5. Make a Screenshot in Case of Error |
|
4-6. Check the Accuracy of Tests Before Adding Them to the Regular Run4-7. Avoid Comparing Images -- Chapter 5: Reviewing -- 5-1. Write Tests That Even Non-Automation Engineers Can Understand -- 5-2. Avoid Unneeded Optimization -- 5-3. Review Someone Elseâ#x80;#x99;s Code Regularly -- 5-4. Participate in Forums and Discussions -- 5-5. Perform Refactoring -- 5-6. Remove Tests That Provide Minimal Benefit |
| Subject |
Computer software -- Testing -- Automation.
|
|
Programming & scripting languages: general. |
|
Computer science |
|
Programming languages (Electronic computers) |
| Other Form: |
Printed edition: 9781484231616 |
| ISBN |
9781484231623 (electronic bk.) |
|
1484231627 (electronic bk.) |
|
1484231619 |
|
9781484231616 |
| Standard No. |
10.1007/978-1-4842-3162-3 doi |
|
More Resources