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) |
(→Test mapping / Test plan configuration) |
||
| Line 6: | Line 6: | ||
# Testplanner reads the configuration/mapping file and creates test plan(s) | # Testplanner reads the configuration/mapping file and creates test plan(s) | ||
# Kickstart files are delivered to image builder and test plans for test automation | # Kickstart files are delivered to image builder and test plans for test automation | ||
| + | |||
| + | Mapping/configuration file: | ||
| + | <pre> | ||
| + | name: Release testing | ||
| + | devices: [ chroot virtual n900 ] | ||
| + | kickstart bases: | ||
| + | chroot: chroot-release.ks | ||
| + | virtual: virtual-image-core.ks | ||
| + | n900: mer-core-n900.ks | ||
| + | default options: | ||
| + | filter: "testset=core" | ||
| + | default package naming: "-tests" | ||
| + | rules: | ||
| + | alc: | ||
| + | -test: acl-tests | ||
| + | -filter: "name=unittests" | ||
| + | -versio: < 1.5.0 | ||
| + | -device: [virtual n900] | ||
| + | |||
| + | </pre> | ||
Revision as of 19:25, 21 April 2012
Test mapping / Test plan configuration
- Test request comes in. The request has parameter such as stage and changed package 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 virtual n900 ]
kickstart bases:
chroot: chroot-release.ks
virtual: virtual-image-core.ks
n900: mer-core-n900.ks
default options:
filter: "testset=core"
default package naming: "-tests"
rules:
alc:
-test: acl-tests
-filter: "name=unittests"
-versio: < 1.5.0
-device: [virtual n900]
