action #60605
closed
coordination #60071: [functional][y][epic] SLE 15 SP2 feature testing
[functional][y][SLE-7373][SLE-7333][timeboxed:30h] snapper create: branch from different snapshot
Added by riafarov over 4 years ago.
Updated over 4 years ago.
Target version:
SUSE QA - Milestone 30
Description
See https://jira.suse.com/browse/SLE-7373 and https://jira.suse.com/browse/SLE-7333
Exploratory manual testing.
Acceptance criteria¶
- Scope of changes is learned
- Exploratory testing is conducted for the parts which are not covered by the automated tests
- Follow-up tickets for automated tests are created with detailed description in case are considered to be useful (efforts vs profit)
- jira ticket is updated accordingly
Suggestion¶
- we should definitely test it with transactional update role
- Subject changed from [functional][y][SLE-7373][SLE-7333] snapper create: branch from different snapshot to [functional][y][SLE-7373][SLE-7333][timeboxed:30h] snapper create: branch from different snapshot
- Description updated (diff)
- Status changed from New to Workable
- Priority changed from Normal to High
- Status changed from Workable to In Progress
- Assignee set to oorlov
- Due date changed from 2019-12-17 to 2019-12-31
- Copied to action #61097: [functional][y][SLE-8787][SLE-8903] Feature testing: Autoyast option for non-secure boot added
- Copied to deleted (action #61097: [functional][y][SLE-8787][SLE-8903] Feature testing: Autoyast option for non-secure boot)
- Target version changed from Milestone 30+ to Milestone 30
bulk moved to M30 for revisiting
- Due date changed from 2019-12-31 to 2020-01-14
Shifting tickets after holiday period.
As agreed with @oorlov, he will provide current achievement and impediments found at the moment. Thanks.
- Status changed from In Progress to Resolved
Feature test passed.
The list of most important covered cases:
- Verified that
--read-write parameter for snapper create creates a snapshot without read only flag (e.g. command to see the flag sudo btrfs subvolume show /.snapshots/4/snapshot);
- Verified that correct parent_uuid is shown for the snapshot created with
--from parameter (e.g. command to see the parent_uuid: sudo btrfs subvolume list / -qu);
- Verified the combination of --read-write and --from;
- Verified on Transactional Server on Tumbleweed, that
transaction-update --continue works correctly.
- Related to action #61991: [y][functional] Add test module for 'snapper create: branch from different snapshot' added
Also available in: Atom
PDF