Meego Wiki
Views

Quality/QA-tools/Test packaging

From MeeGo wiki
(Difference between revisions)
Jump to: navigation, search
(→Open Testing Service Architecture)
Line 32: Line 32:
Tool chain covers all the bits and pieces required for that.
Tool chain covers all the bits and pieces required for that.
-
 
-
=== Tools release schedule ===
 
-
 
-
[http://wiki.meego.com/Quality/QA-tools MeeGo QA tools team] targets following schedule to publish tools for open development:
 
-
 
-
  * test packaging overview, guidelines and examples - June 4th 2010 - OK
 
-
  * [http://gitorious.org/qa-tools/test-definition test plan definition] - validation schemas - June 4th 2010 - OK
 
-
  * [http://gitorious.org/qa-tools/testrunner-lite test plan tool support] - testrunner-lite - June 18th 2010 - OK (June 17th 2010)
 
-
  * [http://gitorious.org/qa-tools/ots OTS core (OTS server and client)] - end of July (target was 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)
 

Revision as of 11:50, 16 September 2010

Contents

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 and the test tools 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.

Retrieved from "http://wiki.meego.com/Quality/QA-tools/Test_packaging"
Personal tools