Alpaev Software Testing Automation Tips

50 Things Automation Engineers Should Know
1. ed
ISBN: 978-1-4842-3162-3
Verlag: Apress
Format: PDF
Kopierschutz: 1 - PDF Watermark

E-Book, Englisch, 58 Seiten

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 LearnEmploy 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
Who This Book Is For
Software test engineers working with automated testing tools, and for developers working alongside testing teams to create software products. The book will aid test engineers, team leads, project managers, software testers, and developers in producing quality software more easily, and in less time.

?Gennadiy Alpaev has been working as a test automation engineer since 2003. He has worked with many automation tools, including SilkTest, TestComplete, Selenium, and Squish. In 2011 he began to move his expertise toward teaching about testing and automation. Gennadiy has been running online and on-site courses on TestComplete and test automation for independent students and companies ever since. He is a published author, and speaks regularly at conferences on the topic of testing automation.

Autoren/Hrsg.

Alpaev, Gennadiy

Inhaltsverzeichnis

1;Contents at a Glance;4
2;Contents;5
3;About the Author;8
4;About the Technical Reviewers;9
5;Introduction;10
6;Chapter 1: Scripting;11
6.1;1-1. Do Not Use Record & Play in Real Projects;11
6.2;1-2. Do Not Use Pauses;13
6.3;1-3. Provide Exit by Timeout for Loops;14
6.4;1-4. Do Not Consider Test Automation as Full-Fledged Development;15
6.5;1-5. Do Not Write Bulky Code;16
6.6;1-6. Verify All Options of Logical Conditions;18
6.7;1-7. Use Coding Standards;18
6.8;1-8. Use Static Code Analyzers;19
6.9;1-9. Add an Element of Randomness to Scripts;20
6.10;1-10. Do Not Perform Blind Clicks Against Nonstandard Controls;20
6.11;1-11. Learn and Use Standard Libraries;21
6.12;1-12. Avoid Copy and Paste;22
6.13;1-13. Do Not Use try…catch with an Empty catch Block;23
6.14;1-14. Separate Code from Data;24
6.15;1-15. Learn How to Debug;25
6.16;1-16. Do Not Write Code for the Future;26
6.17;1-17. Leave the Code Better Than It Was;27
6.18;1-18. Choose a Proper Language for GUI Tests;27
6.19;1-19. Remember to Declare and Initialize Variables;28
7;Chapter 2: Testing;30
7.1;2-1. Do Not Duplicate Tested Application Functionality in the Scripts;30
7.2;2-2. Each Test Should Be Independent;31
7.3;2-3. What Should Not Be Automated?;32
7.4;2-4. Ask the Developers for Help;33
7.5;2-5. Cloud Testing;35
7.6;2-6. Introduce Automation for Corner Cases;35
7.7;2-7. The Difference Between Error and Warning;36
7.8;2-8. Use the Appropriate Methodologies;36
7.9;2-9. Verification of Individual Bugs;37
7.10;2-10. Make a Pilot Project Before Writing Real Tests;38
8;Chapter 3: Environment;39
8.1;3-1. Choose a Proper Set of Tools for Your Needs;39
8.2;3-2. Do Not Automatically Register Bugs from Scripts;40
8.3;3-3. Do Not Chase After a “Green Build” in the Prejudice of Quality;41
8.4;3-4. Learn the Tool You Work With;41
8.5;3-5. Make Use of Version Control Systems;42
8.6;3-6. Avoid Custom Forms;43
8.7;3-7. Simplify Everything You Can;43
8.8;3-8. Automate Any Routine;44
9;Chapter 4: Running, Logging, Verifying;45
9.1;4-1. Run Scripts as Often as Possible;45
9.2;4-2. Perform an Automatic Restart of Failed Tests;46
9.3;4-3. A Disabled Test Should Be Provided with a Comment;46
9.4;4-4. Errors in Logs Should Be Informative;47
9.5;4-5. Make a Screenshot in Case of Error;47
9.6;4-6. Check the Accuracy of Tests Before Adding Them to the Regular Run;48
9.7;4-7. Avoid Comparing Images;49
10;Chapter 5: Reviewing;51
10.1;5-1. Write Tests That Even Non-Automation Engineers Can Understand;51
10.2;5-2. Avoid Unneeded Optimization;52
10.3;5-3. Review Someone Else’s Code Regularly;53
10.4;5-4. Participate in Forums and Discussions;54
10.5;5-5. Perform Refactoring;55
10.6;5-6. Remove Tests That Provide Minimal Benefit;55
11;Index;57