[Test-Announce] [Proposal] TestDays Category TestCase Tags

Hello Testers,

Fedora QA has been hosting loads of test days for sometime (ie 15 test
days/release) which is why we author test cases. These test cases are
sometimes for features which may never see the light of day (at least
not in that particular release).
Sometimes, these test cases are integration test cases and are very
hard to categorize in package-specific test cases. Many times, due to
their non-blocking nature, they are not associated with "Release
Criterion". This makes test cases authored for a particular test day,
extremely hard to find and check for bitrot.

I propose the following:

a) Add a new category Category:CoreOS Test Cases
b) Add new Category TestDay:NAME
c) We already track the release cycle, Category:Fedora 41 Test Days

Benefits:

a) In the long run add more filtering functions to testday-stats on
test cases added
b) Easier navigation of test cases, written just for a test day and
updation of the same
c) Establishing scope for blocking criteria for upcoming features that
get tested in Rawhide Test Days

I would like to know your concerns and comments. If people are okay, I
can go do the homework :)
--
//sumantro
Fedora QE
TRIED AND PERSONALLY TESTED, ERGO TRUSTED
--
_______________________________________________
test-announce mailing list -- test-announce@lists.fedoraproject.org
To unsubscribe send an email to test-announce-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/test-announce@lists.fedoraproject.org
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue