Deprecation of STI tests
Summary
Display a deprecation warning for Fedora 41 for all STI tests. Deprecate execution of STI tests in all CI pipelines for Fedora 42.
- CI for bodhi updates
- CI for dist-git pull requests
All users of STI tests will need to migrate to the new tmt format.
Owner
- Name: Miroslav Vadkerti, Michal Srb,
- Email: mvadkert@redhat.com, msrb@redhat.com
- Email: <your email address so we can contact you, invite you to meetings, etc. Please provide your Bugzilla email address if it is different from your email in FAS>
Current status
- Targeted release: Fedora Linux 41
- Last updated: 2024-06-07
- [Announced]
- [<will be assigned by the Wrangler> Discussion thread]
- FESCo issue: <will be assigned by the Wrangler>
- Tracker bug: <will be assigned by the Wrangler>
- Release notes tracker: <will be assigned by the Wrangler>
Detailed Description
For some time CI testing in Fedora can be defined using two different formats:
- Standard Test Interface (STI)
- Test Management Tool (tmt)
As tmt has matured to a state it can fully replace the STI functionality, we are proposing to drop STI as the supported format. STI format is not actively developed and is causing us a maintenance burden. Moreover, tmt provides a more streamlined experience to discover, execute and debug tests thanks to its tmt
command line tool.
Feedback
Benefit to Fedora
Having two formats for executing the tests is an unnecessary duplication and causes confusion for the Fedora maintainers and community.
STI tests have limited functionality and are harder to develop and maintain, when compared to tmt.
Scope
- Proposal owners:
- Other developers:
- Release engineering: #Releng issue number
- Policies and guidelines: N/A (not needed for this Change)
- Trademark approval: N/A (not needed for this Change)
- Alignment with the Fedora Strategy:
Upgrade/compatibility impact
This is a change to the development experience, no changes to Fedora distribution are made.
Early Testing (Optional)
Do you require 'QA Blueprint' support? Y/N
How To Test
User Experience
Dependencies
Contingency Plan
- Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change)
- Contingency deadline: N/A (not a System Wide Change)
- Blocks release? N/A (not a System Wide Change), Yes/No
Documentation
N/A (not a System Wide Change)