Book Image

Robot Framework Test Automation

By : Sumit Bisht
Book Image

Robot Framework Test Automation

By: Sumit Bisht

Overview of this book

Testing has traditionally been a part of software development, and has always involved a lot of manual effort. It can be automated with Robot Framework, which offers numerous benefits from cost saving to increased quality assurance in the software delivery. This book will help you to start designing test suites and Automated Acceptance Tests. Helping you to get started with automating acceptance tests, this book will provide a detailed overview of acceptance test management practices and principles. You will also be introduced to advanced techniques that you can use to customize the test suite, along with helpful tips and tricks to extend and leverage it in a wide variety of scenarios. Starting with a detailed explanation of the need for automated acceptance test driven development, this guide will help you with an empty test project creation and execution for proof of concept, and validation of installation. This book will also cover the Robot Framework in detail, and will help you test desktop applications using Java Swing. You will gain an in-depth knowledge of tricky activities, such as setting up a test environment and using it with Selenium. You will also learn about other popular libraries, and how to test network protocols, web services, and databases. This book will cover the entire Robot Framework with real- world practical material to make its content informative and interesting. By the end of this book you will be able to write acceptance tests for desktop and web applications, as well as know how to extend acceptance testing in other scenarios that are commonly devoid of tests, and present the results appropriately.
Table of Contents (12 chapters)

Test coloring information

In any xUnit test result, red denotes failure and green denotes success. This coloring has also led to the popular TDD mantra of "Red, Green, Refactor" in unit tests, which denotes the order of development as first the tests are created with an intention to naturally fail followed by writing code in such a manner that the tests pass and finally refactoring over existing code can be made in such a manner that nothing is broken.

The following screenshot demonstrates a test application passing entirely as the green color background is clearly visible:

Similarly, the failure of the test suite can also be reflected through the background color. Note that, even if a single test case fails, the entire report will have the color of failure and the end user can easily take note, as shown in the following screenshot:

This convention is also followed in the Robot Framework as is evident from the report background color as well as the colors used in the executed tests inside the...