action #71044
closed
coordination #70390: [qe-core][epic] post-installation tests for transactional role
[u] extra_tests_transactional_server on Tumbleweed x86_64
Added by SLindoMansilla over 3 years ago.
Updated over 3 years ago.
Target version:
SUSE QA - Milestone 30
Description
Acceptance criteria¶
- AC1: A test suite
extra_tests_transactional_server is schedule on openqa.opensuse.org for Tumbleweed x86_64
- AC2:
extra_tests_transactional_server is scheduled on openqa.opensuse.org for Tumbleweed x86_64 on the main job group only after 2 consecutive green jobs.
Tasks¶
- Create test suite definition on openqa.opensuse.org
- Create YAML schedule in schedules.
- Schedule
extra_tests_transactional_server in Development Tumbleweed on x86_64
- After two consecutive green jobs in
Development Tumbleweed, move it to openSUSE Tumbleweed
Test suite definition¶
Description¶
Maintainer: slindomansilla@suse.de
Mainly post-installation console extra tests.
Settings¶
BSC1167736=1
BOOT_HDD_IMAGE=1
DESKTOP=textmode
HDD_1=SLES-%VERSION%-%ARCH%-Build%BUILD%@%MACHINE%-transactional_server.qcow2
MAX_JOB_TIME=18000
START_AFTER_TEST=create_hdd_transactional_server
YAML_SCHEDULE=schedule/functional/extra_tests_textmode.yaml
- Category set to New test
- Status changed from New to Workable
- Target version set to Milestone 30
- Estimated time set to 42.00 h
The reason why we need a extra_tests_transactional_server is because for SLE, the installation is done in the Yast group (create_hdd_transactional_server).
QSF-U has to avoid testing installations (even more when Yast team is already covering it), so we need extra_tests_transactional_server that reuses the published qcow2 image from create_hdd_transactional_server.
Having different testing jobs for Tumbleweed, SLE and Leap would be a pain for QSF-U to maintain.
This ticket is separated from the SLE one for simplicity and following Factory first policy.
The acceptance criteria and tasks of the ticket are still valid.
there is no transactional_server.qcow2 available on O3 for TW. So we need to create this at first and add a test suite.
zluo wrote:
there is no transactional_server.qcow2 available on O3 for TW. So we need to create this at first and add a test suite.
Yes.
And when create_* and extra_* are in place and covering at least the same post installation modules, I will propose to remove transactional_server to avoid duplication.
- Status changed from Workable to In Progress
- Status changed from In Progress to Resolved
Also available in: Atom
PDF