Ahmedalmeleh (talk | contribs) |
Ahmedalmeleh (talk | contribs) |
||
| Line 28: | Line 28: | ||
== Prerequisite for Test Day == | == Prerequisite for Test Day == | ||
Fully updated F36 / Rawhide test day image or installation | Fully updated F36 / Rawhide test day image or installation (Any edition / spin / lab) either on bare metal or VM (please make sure you have no important data on that installation, things might go wrong -- don't do this on your production machine!) | ||
A web browser to load any website on. A terminal to enter the command on. (GNOME Terminal should be fine.) | |||
A web browser to load any website on. | |||
A terminal to enter the command on. (GNOME Terminal should be fine.) | |||
Enough free space on HDD | Enough free space on HDD | ||
Revision as of 15:38, 16 November 2021
| DNS Over TLS Test day | |
|---|---|
| |
| Date | 2021-12-02 0:00 UTC to 2021-12-02 23:59 UTC |
| 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?
This Test Day will focus on DNS Over TLS Primary aim is to test on Fedora 36 / Rawhide.
Who's available
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion:
- Development - Developer1 (irc_nick1), Developer2 (irc_nick2) FIXME
- 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
Fully updated F36 / Rawhide test day image or installation (Any edition / spin / lab) either on bare metal or VM (please make sure you have no important data on that installation, things might go wrong -- don't do this on your production machine!)
A web browser to load any website on. A terminal to enter the command on. (GNOME Terminal should be fine.) Enough free space on HDD
How to test?
Load any website in a web browser. If you succeed, then name resolution probably works.
Try using resolvectl query fedoraproject.org to see that resolvectl still works.
Bonus points: set your DNS server to 1.1.1.1 or 8.8.8.8, then use Wireshark to see if your DNS is really encrypted or not.
If not using the TestDays app, provide a list of test areas or test cases that you'd like contributors to execute. For examples, see https://fedoraproject.org/wiki/Category:Test_Cases . If possible, always include https://fedoraproject.org/wiki/QA:Testcase_Exploratory_Testing among test cases. If using the TestDays app, link the test cases in it. -->
Visit the results 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.
Please also try to experiment and explore and perform tasks not mentioned in any of the pre-defined test cases.
Reporting bugs
All bugs should be reported into Bugzilla, in most cases against the FIXME component. If you are unsure about exactly how to file the report or what other information to include, just ask us on IRC (see instructions above).
Test Results
Test results will be exported here once the test day is over. See How to test? section for information how to submit results and see the live results.