Skip to main content

Über dieses Buch

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

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.



Chapter 1. Scripting

This chapter describes best practices in automation related to writing code, creating tests, and building your automation framework. Also mentioned are some of the common mistakes that automation engineers produce in their work, and ways to avoid those mistakes. Some tips in this chapter are common for both automation and development, while others are specific for testing automation only.
Gennadiy Alpaev

Chapter 2. Testing

However, there are some rules we should take into account when automating existing test cases and user cases, or when we decide what should be automated and what should stay for manual execution. This chapter describes best practices related to the testing process and the relationship between manual and automated testing.
Gennadiy Alpaev

Chapter 3. Environment

There are two main types of environments in software testing automation. The first of them is the one we use to create and debug tests, and another one is used for running tests against tested applications.
Gennadiy Alpaev

Chapter 4. Running, Logging, Verifying

When running your tests against tested application, it is very important to have a detailed report with comprehensive messages about any issues tests faced during the run. It is also important to decide how to organize your tests’ run and how often tests should be run. This chapter describes some of the best practices in software testing automation related to running tests and creating logs for further investigation.
Gennadiy Alpaev

Chapter 5. Reviewing

The review process is a good way to keep your code clear and understandable. It is important both to review others’ code and having your own code reviewed, not depending on how many years you have been working in the project or how much experience you have gotten. This chapter describes several cases when it is important to review or optimize your tests, or vice versa – when it is better to do nothing instead.
Gennadiy Alpaev


Weitere Informationen

Premium Partner

BranchenIndex Online

Die B2B-Firmensuche für Industrie und Wirtschaft: Kostenfrei in Firmenprofilen nach Lieferanten, Herstellern, Dienstleistern und Händlern recherchieren.



Best Practices für die Mitarbeiter-Partizipation in der Produktentwicklung

Unternehmen haben das Innovationspotenzial der eigenen Mitarbeiter auch außerhalb der F&E-Abteilung erkannt. Viele Initiativen zur Partizipation scheitern in der Praxis jedoch häufig. Lesen Sie hier  - basierend auf einer qualitativ-explorativen Expertenstudie - mehr über die wesentlichen Problemfelder der mitarbeiterzentrierten Produktentwicklung und profitieren Sie von konkreten Handlungsempfehlungen aus der Praxis.
Jetzt gratis downloaden!