Test Packaging

The following test packaging description is for MeeGo stakeholder comments

Contents 1 Introduction 2 Open Testing Service Architecture 3 Test packaging rules 4 Test plan definition 5 Tool support 5.1 Tools release schedule 6 Footnotes

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 (documentation to be moved here).

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 and the test tools it depends on (if any)
• contain test plan located at /usr/share/<testpackagename>/tests.xml [1]

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.

Tools release schedule

MeeGo QA Tools team targets following schedule to clear tools for open development:

 * test packaging overview, guidelines and examples - June 4th 2010
 * test plan definition - validation schemas - June 4th 2010
 * test plan tool support - testrunner-lite - June 18th 2010 (requires removal of dependency to closed hwinfo tool on arm targets)
 * OTS core (OTS server and client) - 2nd week of July  
 * description of automated software update for mobile devices and netbooks - end of July

Tools referred above have been developed inside Nokia and Intel for some years - releasing them open source requires legal clearance to honor various open source licenses.

Footnotes

[1] location currently used with deb-version of test packaging, to be re-checked with FHS - filesystem hierarchy standard)