action #30433
closed
coordination #12808: [sle][opensuse][functional][y][epic] Adapt testsuite textmode for ncurses - WAS(Update partitioning_filesystem for textmode installations)
[opensuse][functional][y][easy] Enable tests for module "partitioning_filesystem" for openSUSE (O3) in *textmode*
Added by SLindoMansilla over 6 years ago.
Updated almost 6 years ago.
Target version:
SUSE QA - Milestone 17
Description
Acceptance criteria¶
- AC1: The offered file systems (ext3, btrfs, xfs) are covered for the / partition by automated tests in textmode for openSUSE distributions
Tasks¶
- Add a (sparse?) test matrix covering the fs' ext3, btrfs, xfs in textmode for openSUSE Tumbleweed + ports as well as Leap. For example:
- textmode+ext3, textmode+xfs, textmode+btrfs on TW x86_64
- same on TW ppc64le, potentially only one or two of the scenarios
3. same on TW aarch64 (not official support)
4. same on Leap (We are late for that, Leap was released)
5. same on Leap ports (We are late for that, Leap was released)
- Blocked by action #27961: [opensuse][sle][story][medium] Adapt **partitioning_filesystem** for ncurses added
- Description updated (diff)
- Category set to New test
- Status changed from New to Workable
- Due date set to 2018-03-27
- Target version set to Milestone 15
I'm not sure about this one. What exactly is missing here? Is it about executing the partitioning_filesystem particularly in textmode on o3?
- Description updated (diff)
- Status changed from Workable to New
Yes, that was the initial issue raised by Dirk Müller. The initial issue is on the parent ticket, the epic one.
They wanted to have this test suite on TW on textmode.
So, we have ext3 test suite which is graphical. And we need a new test suite ext3-textmode?
And so for btrfs and xfs too.
Chaging the status to new. Tasks updated. Please set status workable if you think it is clear enough.
- Subject changed from [opensuse][story][easy] Enable tests for module "partitioning_filesystem" for openSUSE (O3) to [opensuse][story][easy] Enable tests for module "partitioning_filesystem" for openSUSE (O3) in *textmode*
- Description updated (diff)
Maybe a sparse test matrix is good enough for us. Updating ACs and tasks
- Status changed from New to Workable
- Subject changed from [opensuse][story][easy] Enable tests for module "partitioning_filesystem" for openSUSE (O3) in *textmode* to [opensuse][functional][story][easy] Enable tests for module "partitioning_filesystem" for openSUSE (O3) in *textmode*
- Due date deleted (
2018-03-27)
- Target version changed from Milestone 15 to Milestone 17
no capacity in M15 or M16 left
- Subject changed from [opensuse][functional][story][easy] Enable tests for module "partitioning_filesystem" for openSUSE (O3) in *textmode* to [opensuse][functional][y][easy] Enable tests for module "partitioning_filesystem" for openSUSE (O3) in *textmode*
- Due date set to 2018-06-19
- Assignee set to JERiveraMoya
- Description updated (diff)
- Status changed from Workable to Feedback
- Description updated (diff)
- Status changed from Feedback to In Progress
Created in O3 the following test suites:
- openSUSE Tumbleweed: ext4_textmode, ext3_textmode, xfs_textmode and btrfs_textmode. Added to Jobs Groups in opensuse-DVD section with architecture 64bit.
- openSUSE Tumbleweed PowerPC: ext4_textmode. Added to Jobs Groups in opensuse-DVD section with architecture ppc64le (it does not look outdated, openSUSE Tumbleweed PowerPC build 20180530 is from 5 days ago)
- Status changed from In Progress to Resolved
- Status changed from Resolved to Feedback
Please, don't resolve this ticket until you have a verification run from O3.
- Status changed from Feedback to Resolved
Right, thanks for the reminder.
VRs in O3:
- Status changed from Resolved to Feedback
Sorry for the ping-pong.
This is a special case where new test suites are scheduled, so the way to verify that is waiting for the next build.
Please, resolve when those verification are available.
Don't worry for the ping-pong :) I will wait, is true, a little strict, but we can always forget some parameter in the scheduling. Let's wait then. Thanks for the support.
- Status changed from Feedback to Resolved
VRs in O3 (scheduled ;) ):
- Target version changed from Milestone 17 to Milestone 17
Also available in: Atom
PDF