From Fedora Project Wiki

Revision as of 18:24, 2 April 2024 by Jflory7 (talk | contribs) (Jflory7 moved page User:Sumantrom/Draft/QA:SOP rawhide tesday to User:Sumantrom/Draft/QA:SOP Rawhide TestDay: Fix spelling error)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Rawhide Test Days

Introduction

Fedora Quality Assurance (QA) is dedicated to ensuring the stability, reliability, and functionality of Fedora Linux distributions. As part of this commitment, we recognize the importance of Rawhide Test Days in facilitating early testing of system-wide changes and self-contained features destined for future Fedora releases. This SOP outlines the objectives, scope, and benefits of Rawhide Test Days, aimed at fostering collaboration, enhancing testing practices, and delivering a more robust Fedora ecosystem.

Objectives

The primary objectives of Rawhide Test Days are as follows:

a) Early Testing for Timely Delivery: Rawhide Test Days facilitate early testing of changes intended for future Fedora releases. By testing these changes ahead of time, we aim to identify and address potential issues proactively, thereby ensuring timely delivery of Fedora releases.

b) Adding Test Cases for Upcoming Changes: Through Rawhide Test Days, we seek to develop and incorporate test cases for upcoming changes into the testing framework. These test cases will assist maintainers in documenting "how to test" instructions for specific release cycles, thereby improving the testing process and overall quality of Fedora releases.

c) Encouraging Timely Submissions: Rawhide Test Days serve as a platform to discourage last-minute submissions in the Changes Process Deadline. By encouraging early testing and feedback, we aim to promote a culture of timely submissions, ensuring smoother integration of changes into Fedora releases.

d) Building Trust and Collaboration: We aim to foster trust and collaboration within the Fedora community, particularly within sub-communities such as Podman and Podman Desktop. Rawhide Test Days provide an opportunity for these sub-communities to devise their testing scenarios and contribute to the development of more defined test cases. This collaborative approach strengthens the Fedora ecosystem and enhances the quality of testing practices.

e) Empowering Downstream QE Participation: Rawhide Test Days aim to empower downstream Quality Engineering (QE) teams by providing them with more lead time and opportunities for participation. By conducting comprehensive testing early in the development cycle, downstream QE teams can better prepare for upcoming Fedora releases, leading to improved downstream product quality and stability.

Scope

The scope of Rawhide Test Days encompasses the following:

  • Testing of system-wide changes and self-contained features intended for inclusion in future Fedora releases.
  • Development and incorporation of test cases for upcoming changes into the testing framework.
  • Collaboration with sub-communities such as Podman and Podman Desktop to devise testing scenarios and refine test cases.
  • Early identification and resolution of issues to ensure timely delivery of Fedora releases.
  • Encouraging timely submissions in the Changes Process Deadline to streamline the integration of changes into Fedora releases.
  • Empowering downstream QE teams by providing them with more lead time and opportunities for participation in testing activities.

Conclusion

Rawhide Test Days play a vital role in enhancing the testing practices, collaboration, and overall quality of Fedora Linux distributions. By conducting early testing of changes and fostering collaboration within the community, we strive to deliver Fedora releases on time with improved stability and reliability. Through this SOP, we reaffirm our commitment to maintaining the high standards of quality assurance within the Fedora ecosystem.