This is the third installment in the Notes on Test Automation series.
So far I have published one article in this series about Test Encapsulation, which focuses on making tests the most powerful part of a framework, and one about Distributed Testing Models, in which various types of implementation of distributed testing and their pros/cons were discussed. In this article, I am going to discuss formats of test configuration as applicable to the design of Test Automation Frameworks (hereafter referred to as TAFs).
A TAF under most scenarios would provide a mechanism for the end user to configure tests for a test cycle, in which various properties can be configured. Even in basic TAFs, this is kept outside of the code for ease of use, maintainability etc. Some common configurable properties which a TAF can provide via a test configuration include specifying the tests to be executed, the build under test, type of build, minimum priority of tests to be run, whether only tests that have known associated bugs are to be executed, and so on.

The article is available as a PDF file here (~ 0.65 MB): Notes on Test Automation – Test Configuration Formats
You can also download the complete magazine  from the Testing Experience website after a small registration process.
Rahul Verma

2 Responses to “Notes on Test Automation (III) – Test Configuration Formats”

  1. Lisa Davidson

    Very nice post. Thanks for sharing your views on Test Automation Frameworks. I was looking for such expert information on Software Test Automation, tolls and frameworks.

  2. Rahul Verma

    Thanks for the appreciation.

    I’d write on another topic under this series in Q4, 2011

Leave a Reply


1 2 12
June 30th, 2020

Arjuna 1.1.0 Production Release

July 23rd, 2017

The Last Keynote on Software Testing

July 23rd, 2017

The Agile Qtopia

July 23rd, 2017

Reflections:: Persistent Learning

February 28th, 2017

Reflections :: Servitude

January 9th, 2017

Reflections on Testing: Dignity

May 10th, 2016

The Pluralistic School of Testing

May 9th, 2016

Don’t Ignore Your Special Users

May 9th, 2016

The Dogmatic Agile – A Critique of Deliberate Blindness

October 9th, 2015

Pattern Thinking for Performance Engineers