The Mer Wiki now uses your Mer user account and password (create account on https://bugs.merproject.org/)
Talk:Quality/Test processes
From Mer Wiki
(Difference between revisions)
(→Test mapping / Test plan configuration) |
|||
| Line 25: | Line 25: | ||
filter: "hardware=chroot" | filter: "hardware=chroot" | ||
- all: | - all: | ||
| − | test package | + | test package suffix: "-tests" |
default packages: | default packages: | ||
| Line 58: | Line 58: | ||
* default options: default options for devices | * default options: default options for devices | ||
** filter: filter options to testrunner-lite | ** filter: filter options to testrunner-lite | ||
| − | ** test package | + | ** test package suffix: if test package(s) are not defined for a package, then trying to use "original package name + suffix" test package. See the bluez package below. |
* default packages: a list of test packages that are always executed | * default packages: a list of test packages that are always executed | ||
* packages: the actual package mapping | * packages: the actual package mapping | ||
Revision as of 05:46, 23 April 2012
Test mapping / Test plan configuration
- Test request comes in. The request has parameters such as stage and "changed packages" list
- Testplanner reads the configuration/mapping file and creates test plan(s)
- Kickstart files are delivered to image builder and test plans for test automation
Mapping/configuration file:
name: Release testing
devices:
- chroot
ots-device: mer-chroot
kickstart: chroot-release.ks
- virtual
ots-device: mer-virtual-i686
kickstart: virtual-image-core.ks
- n900
ots-device: mer-n900
kickstart: nemo-n900.ks
default options:
- chroot:
filter: "hardware=chroot"
- all:
test package suffix: "-tests"
default packages:
- chroot:
- mer-core-chroot-tests
- all:
- mer-core-sanity-tests
packages:
- alc:
filter: "name=unittests"
versio: < 1.5.0
device: [virtual n900]
- bluez
- qt5base:
test packages:
- mwts-location-tests
filter: "type=functional"
versio: 2.3.1
device: [virtual n900]
- qt5base-unittests
Description:
- devices: a list of devices for the tests are executed
- ots-device: device name in the OTS (test automation)
- kickstart: mapping kickstart files to devices
- default options: default options for devices
- filter: filter options to testrunner-lite
- test package suffix: if test package(s) are not defined for a package, then trying to use "original package name + suffix" test package. See the bluez package below.
- default packages: a list of test packages that are always executed
- packages: the actual package mapping
- filter: filter options to testrunner-lite
- version: package version to use
- device: on which devices to execute the test
- test packages: list of test packages and their configurations
