From Fedora Project Wiki

 
(10 intermediate revisions by 3 users not shown)
Line 3: Line 3:
| name = '''DNS Over TLS Test day'''
| name = '''DNS Over TLS Test day'''
| image = [[File:test-days-banner.svg|300px|link=QA/Test Days]]
| image = [[File:test-days-banner.svg|300px|link=QA/Test Days]]
| date = '''2021-12-02 0:00 UTC to 2021-12-02 23:59 UTC'''
| date = '''2021-12-30'''
<!-- The testdays app will parse this, so please make sure to have it in format 'date = YYYY-MM-DD' or 'date = YYYY-MM-DD to YYYY-MM-DD' -->
| time = all day
| time = all day
| website = [[QA/Test Days]]
| website = [[QA/Test Days]]
Line 14: Line 13:


== What to test? ==
== What to test? ==
<!-- Describe in detail what this test day is about and why would users want to participate in it. What makes this interesting for them? What's new and exciting in your software or a feature? -->


This [[QA/Test Days|Test Day]] will focus on '''DNS Over TLS''' Primary aim is to test on Fedora 36 / Rawhide.
This [[QA/Test Days|Test Day]] will focus on '''DNS Over TLS''' Primary aim is to test on Fedora 36 / Rawhide.
Line 22: Line 19:


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:
* Development - [[User:Developer1|Developer1]] (irc_nick1), [[User:Developer2|Developer2]] (irc_nick2) '''FIXME'''
* Development - [[User:Zbyszek|Michael Catanzaro]] (zbyszek)
* Quality Assurance - [[User:Sumantrom|Sumantro Mukherjee]] (sumantrom), [[User:coremodule|Geoffrey Marr]] (coremodule), [[User:kparal|Kamil Paral]] (kparal), [[User:adamw|Adam Williamson]] (adamw)
* Quality Assurance -  [[User:Ahmedalmeleh|Ahmed Almeleh]] (Ahmedalmeleh) [[User:Sumantrom|Sumantro Mukherjee]] (sumantrom), [[User:coremodule|Geoffrey Marr]] (coremodule), [[User:kparal|Kamil Paral]] (kparal), [[User:adamw|Adam Williamson]] (adamw)


You can chat with us on [[How to use IRC|IRC]]. See the infobox on top of the page to learn the right IRC channel.
You can chat with us on [[How to use IRC|IRC]]. See the infobox on top of the page to learn the right IRC channel.


== Prerequisite for Test Day ==  
== 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!)
* 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 web browser to load any website on.  
A terminal to enter the command on. (GNOME Terminal should be fine.)
* A terminal to enter the command on. (GNOME Terminal should be fine.)
Enough free space on HDD
* Enough free space on HDD


== How to test? ==
== How to test? ==


Load any website in a web browser. If you succeed, then name resolution probably works.
* 1. Load any website in a web browser. If you succeed, then name resolution probably works.
 
* 2. Try using resolvectl query fedoraproject.org to see that resolvectl still 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.
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 '''[http://testdays.fedorainfracloud.org/events/126 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.
-->
 
Visit the '''[http://testdays.fedorainfracloud.org/events/NUMBER 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.
Please also try to experiment and explore and perform tasks not mentioned in any of the pre-defined test cases.


== Reporting bugs ==
== Reporting bugs ==
 
All bugs should be reported into '''[https://bugzilla.redhat.com Bugzilla]''', in most cases against the <code></code> 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).
<!--
If there are multiple places where to report bugs (e.g. general GNOME bugs go into upstream GNOME GitLab, and only packaging issues or non-GNOME bugs go to Red Hat Bugzilla), mention it and advise users where to file which issues.
-->
 
All bugs should be reported into '''[https://bugzilla.redhat.com Bugzilla]''', in most cases against the <code>FIXME</code> 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 ==
Line 61: Line 48:
Test results will be exported here once the test day is over. See [[#How_to_test?|How to test?]] section for information how to submit results and see the live results.
Test results will be exported here once the test day is over. See [[#How_to_test?|How to test?]] section for information how to submit results and see the live results.


<!--
If you're not using TestDays app for submitting test results, and want to let users input results directly into wiki, here's an example results table:
{|
! User
! [[QA:Testcase_example_1|Example test 1]]
! [[QA:Testcase_example_2|Example test 2]]
! [[QA:Testcase_example_3|Example test 3]]
! [[QA:Testcase_example_4|Example test 4]]
! References
|-
| [[User:ExampleUser|Example User]]
| {{result|none}}
| {{result|pass}}
| {{result|warn}} <ref>Test pass, but also encountered {{bz|54321}}</ref>
| {{result|fail}} <ref>{{bz|12345}}</ref>
| <references/>
|-
|}
-->
<!-- uncomment this line when creating a real Test Day
[[Category:Fedora 36 Test Days]]
[[Category:Fedora 36 Test Days]]
-->
<!-- remove the line below when creating a real Test Day -->
[[Category:QA Templates]]

Latest revision as of 00:26, 15 December 2021

DNS Over TLS Test day
Test-days-banner.svg

Date 2021-12-30
Time all day

Website QA/Test Days
IRC #fedora-test-day (webirc)
Mailing list test


Note.png
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.

What to test?[edit]

This Test Day will focus on DNS Over TLS Primary aim is to test on Fedora 36 / Rawhide.

Who's available[edit]

The following cast of characters will be available testing, workarounds, bug fixes, and general discussion:

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]

  • 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?[edit]

  • 1. Load any website in a web browser. If you succeed, then name resolution probably works.
  • 2. 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.

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[edit]

All bugs should be reported into Bugzilla, in most cases against the 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[edit]

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.