From Fedora Project Wiki
| Gitlab Test Day | |
|---|---|
| |
| Date | TBD |
| Time | all week |
| Website | QA/Test Days |
| Matrix | #test-day:fedoraproject.org |
| Mailing list | test |
Can't make the date?
If you come to this page before or after the test day is completed, your testing is still valuable, and you can use the information on this page to test, file any bugs you find at Bugzilla, and add your results to the results section. If this page is more than a month old when you arrive here, please check the current schedule and see if a similar but more recent Test Day is planned or has already happened.
If you come to this page before or after the test day is completed, your testing is still valuable, and you can use the information on this page to test, file any bugs you find at Bugzilla, and add your results to the results section. If this page is more than a month old when you arrive here, please check the current schedule and see if a similar but more recent Test Day is planned or has already happened.
What to test?[edit]
This Test Day will focus on the Fedora Dist-Git Evaluation.
Who's available[edit]
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion:
- Development - TBD
- Quality Assurance - Sumantro Mukherjee (sumantrom), Geoffrey Marr (coremodule), Kamil Paral (kparal), Adam Williamson (adamw)
You can chat with us on IRC. See the infobox on top of the page to learn the right IRC channel.
Prerequisite for Test Day[edit]
- This is a Gitforge eval, so grab some workflows that you deeply care about
Following are the User Stories..
- As a package maintainer, I’d like to be able to run my own CI jobs on distgit PRs.
- As a package maintainer, I’d like to be able to control the-new-hotness monitoring status from distgit.
- As a provenpackager, I should have push and merge access to all packages in the Fedora package collection.
- Try them up in Gitlab and/or Forgeo
- Report your results on how the workflow went for you
How to evaluate?[edit]
walk the following steps[edit]
- Visit the result page and enter your result in the 'Regression' column by clicking Enter result.
- If there are any other result columns, click on the column title links to see the tests that need to be run: most column titles are links to a specific test case. Follow the instructions there, then enter your results by clicking the Enter result button for the test.
- While the results from the regression tests are interesting, we are also interested in your overall experience with the new kernels. You can put those under QA:Testcase Exploratory Testing.
Report[edit]
If you have problems with any of the tests, have a look in the results page. Please include the hickups and other report in the comments.
Test Results[edit]
The results will be transferred once the test week is complete