Quality/QA-tools/Test packaging

Revision as of 06:45, 28 October 2010

Introduction

Test packaging is intended to provide flexible and consistent ways to run tests and get results. You may select testing tools of your choice.

Test packaging is set of simple rules to wrap tests with test plan inside rpm package. Tool support for validating test plan and automating test plan execution is provided with testrunner. Following describes rpm-version of test packaging.

Open Testing Service Architecture

The context of test package usage is described in Open Testing Service (OTS) architecture.

Test packaging rules

A source package with test cases must:

• build binary rpm package with name which ends with "-tests" (this is a test package)

A test package must:

• contain all tests, scripts and configuration files required to run tests
• define dependencies - the ones it tests, the test tools and test data it depends on (if any)
• contain test plan located at /usr/share/<packagename>-tests/tests.xml [1]

For details on creating a test package, see Creating a test package.

Test plan definition

tests.xml describes what test cases this package has. The file must conform to the specification described in Test Definition XML.

Tool support

OTS takes care of automated testing with test packages in cloud. Highest level of automation in this context means one-button test automation triggered with version control update, ending up in test run results in target hardware published.

Tool chain covers all the bits and pieces required for that.