action #116299
closedMove non-stable test modules in test suite yast2_cmd to development group
0%
Description
Motivation¶
Test modules in this test suites inherited from previous qam team do not stop to waste our time with timeout issues in slower architectures.
It is time to move them to development group and rethink what to do with them without the need of reviewing them each time, hacking the ram, the timeout or the whole test suite.
Last occurrence:
yast_keyboard
Scope¶
Collect all non-stable test module failing sporadically at least for this first alpha builds in SLE-15-SP5.
Acceptance criteria¶
AC1: All test modules with sporadic failures in test suite yast2_cmd
are moved to development group for further investigation
Additional information¶
Further investigation means, not now, we can create tickets for them later when we analyze how they are build, most likely the problem is they are not only checking YaST-related configuration, but doing things for reals and there might be other squads more interested on this kind of testing.
Updated by JRivrain about 2 years ago
- Tags set to qe-yast-refinement
- Project changed from openQA Tests to qe-yam
- Category deleted (
Bugs in existing tests)
Updated by JERiveraMoya about 2 years ago
- Subject changed from Investigate sporadic failures in yast_keyboard to Move non-stable test modules in test suite yast2_cmd to development group
- Description updated (diff)
- Status changed from New to Workable
Updated by tinawang123 about 2 years ago
- Tags deleted (
qe-yast-refinement) - Assignee set to tinawang123
Updated by tinawang123 about 2 years ago
- Status changed from Workable to In Progress
Updated by tinawang123 about 2 years ago
Found those test moudles are not stable in yast2_cmd
yast_keyboard
9 times
yast_dns_server
9 times
yast_rdp
Only one time because network problem. I believe we don't need move this test module to development job group.
yast_users
1 time
yast_lan
1 time
Updated by tinawang123 about 2 years ago
Updated by tinawang123 about 2 years ago
Updated by tinawang123 about 2 years ago
- Status changed from In Progress to Resolved