Software testing automation tips : 50 things automation engineers should know /: 50 things automation engineers should know. ([2017])
- Record Type:
- Book
- Title:
- Software testing automation tips : 50 things automation engineers should know /: 50 things automation engineers should know. ([2017])
- Main Title:
- Software testing automation tips : 50 things automation engineers should know
- Further Information:
- Note: Gennadiy Alpaev.
- Authors:
- Alpaev, Gennadiy
- Contents:
- ""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 Controls""""1-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 Independent""""2-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:""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 Controls""""1-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 Independent""""2-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;#x9C;Green Buildâ#x80;#x9D; in the Prejudice of Quality""""3-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 Run""""4-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"" … (more)
- Publisher Details:
- Berkeley, CA : Apress
- Publication Date:
- 2017
- Copyright Date:
- 2017
- Extent:
- 1 online resource
- Subjects:
- 005.14
Computer science
Computer software -- Testing -- Automation
COMPUTERS -- Software Development & Engineering -- Quality Assurance & Testing
Computers -- Programming Languages -- General
Programming & scripting languages: general
Electronic books - Languages:
- English
- ISBNs:
- 9781484231623
1484231627
1484231619
9781484231616 - Related ISBNs:
- 9781484231616
- Notes:
- Note: Online resource; title from PDF title page (EBSCO, viewed November 03, 2017).
- Access Rights:
- Legal Deposit; Only available on premises controlled by the deposit library and to one user at any one time; The Legal Deposit Libraries (Non-Print Works) Regulations (UK).
- Access Usage:
- Restricted: Printing from this resource is governed by The Legal Deposit Libraries (Non-Print Works) Regulations (UK) and UK copyright law currently in force.
- View Content:
- Available online (eLD content is only available in our Reading Rooms) ↗
- Physical Locations:
- British Library HMNTS - ELD.DS.347809
- Ingest File:
- 01_302.xml