| Line 17: | Line 17: | ||
== Who's available == | == Who's available == | ||
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion . | The following cast of characters will be available testing, workarounds, bug fixes, and general discussion. In case of problem related to test day organization/wiki/whatever, please reach out to szidek. | ||
* Development - [[User:Nmav|Nikos Mavrogiannopoulos]] (nmav, GnuTLS, crypto-policies), [[User:Tmraz|Tomáš Mráz]] (t8m, OpenSSL), Kai Engert (kaie, NSS), [[User:Rrelyea|Robert Relyea]] (rrelyea, NSS), [[User:Ueno|Daiki Ueno]] (ueno, NSS), [[User:Jjelen|Jakub Jelen]] (jjelen, OpenSSH) | * Development - [[User:Nmav|Nikos Mavrogiannopoulos]] (nmav, GnuTLS, crypto-policies), [[User:Tmraz|Tomáš Mráz]] (t8m, OpenSSL), Kai Engert (kaie, NSS), [[User:Rrelyea|Robert Relyea]] (rrelyea, NSS), [[User:Ueno|Daiki Ueno]] (ueno, NSS), [[User:Jjelen|Jakub Jelen]] (jjelen, OpenSSH) | ||
* Quality Assurance - [[User:Szidek|Stanislav Židek]] (szidek), [[User:Hkario|Hubert Kario]] (hkario) | * Quality Assurance - [[User:Szidek|Stanislav Židek]] (szidek), [[User:Hkario|Hubert Kario]] (hkario) | ||
Revision as of 10:43, 29 March 2017
| Crypto Policies | |
|---|---|
| |
| Date | 2017-03-30 |
| Time | all day |
| Website | QA/Test Days |
| IRC | #fedora-test-day (webirc) |
| Mailing list | test |
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?
Today's instalment of Fedora Test Day will focus on crypto-policies
Who's available
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion. In case of problem related to test day organization/wiki/whatever, please reach out to szidek.
- Development - Nikos Mavrogiannopoulos (nmav, GnuTLS, crypto-policies), Tomáš Mráz (t8m, OpenSSL), Kai Engert (kaie, NSS), Robert Relyea (rrelyea, NSS), Daiki Ueno (ueno, NSS), Jakub Jelen (jjelen, OpenSSH)
- Quality Assurance - Stanislav Židek (szidek), Hubert Kario (hkario)
Prerequisite for Test Day
- An updated Fedora 26 workstation or server pre-release], or a Fedora 26 nightly image
- helper script to generate TLS certificates or know-how needed to do it yourself
- a desire to break software ;)
How to test?
Update your machine
If you're running Fedora 26, make sure you have all the current updates for it installed, using the update manager. If you want to try Rawhide, see the instructions on the Rawhide page on the various ways in which you can install or update to Rawhide. Or:
Live image
Instead of testing with an installed system, you may download a non-destructive nightly live image for your architecture. Tips on using a live image are available at FedoraLiveCD. Live image links can be found here: please be sure to download one for the correct release.
Run the tests
Visit the result page and 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.
Reporting bugs
Include some instructions on how to report bugs, and any special instructions. Here's an example, from a Palimpsest test day:
If you have problems with any of the tests, report a bug to Bugzilla usually for the component crypto-policies, or for particular software using crypto-policies. If you are unsure about exactly how to file the report or what other information to include, just ask on IRC and we will help you.
Test Results
Please enter your results on the result page. The results will be transferred here after the Test Day is finished.