From Fedora Project Wiki

(14 intermediate revisions by 8 users not shown)
Line 14: Line 14:
== What to test? ==
== What to test? ==


Today's instalment of Fedora Test Day will focus on Network Manager integration with DNSSEC-trigger.
Today's installment of Fedora Test Day will focus on Network Manager integration with DNSSEC-trigger.


== Who's available ==
== Who's available ==
Line 29: Line 29:
== How to test? ==
== How to test? ==
# Install: {{package|dnssec-trigger}}
# Install: {{package|dnssec-trigger}}
# Enable DNSSEC and unbound services: {{command|systemctl enable dnssec-triggerd}}; {{command|systemctl enable unbound}}
# Enable DNSSEC and unbound services: {{command|systemctl enable dnssec-triggerd.service}}; {{command|systemctl enable unbound.service}}
# Restart your computer.
# Restart your computer.


== Test Cases ==
== Test Cases ==
* [[QA:Testcase_DNSSEC-trigger|DNSSEC-trigger]]
* [[QA:Testcase_DNSSEC-trigger|DNSSEC-trigger]]
* [[QA:Testcase_DNS-over-SSL|DNS-over-SSL]]


== Test Results ==
== Test Results ==


Construct a table or list to allow testers to post results.  Each column should be a test case or configuration, and each row should consist of test results. 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 [https://bugzilla.redhat.com Bugzilla] usually for the component [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=18&component=dnssec-trigger dnssec-trigger]. 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. Once you have completed the tests, add your results to the Results table below, following the example results from the first line as a template. The first column should be your name with a link to your User page in the Wiki if you have one. For each test case, use the [[Template:result|result template]] to enter your result, as shown in the example result line.
 
If you have problems with any of the tests, report a bug to [https://bugzilla.redhat.com Bugzilla] usually for the component [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=13&component=udisks udisks], or [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=13&component=gnome-disk-utility gnome-disk-utility] for bugs in the Palimpsest graphical front end itself. 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. Once you have completed the tests, add your results to the Results table below, following the example results from the first line as a template. The first column should be your name with a link to your User page in the Wiki if you have one, and the second should be a link to the Smolt profile of the system you tested. For each test case, use the [[Template:result|result template]] to enter your result, as shown in the example result line.


{|
{|
! User
! User
! Smolt Profile
! [[QA:Testcase_DNSSEC-trigger|DNSSEC-trigger]]
! [[QA:Testcase_sample_1|Sample test 1]]
! [[QA:Testcase_DNS-over-SSL|DNS-over-SSL]]
! [[QA:Testcase_sample_2|Sample test 2]]
! [[QA:Testcase_sample_3|Sample test 3]]
! [[QA:Testcase_sample_4|Sample test 4]]
! References
! References
|-
|-
| [[User:SampleUser|Sample User]]
| [[User:SampleUser|Sample User]]
| [http://www.smolts.org/client/show/pub_84465125-1350-4f83-87b9-5f16f7430eb8 HW]
| {{result|none}}
| {{result|pass}}
| {{result|warn}} <ref>Test pass, but also encountered {{bz|54321}}</ref>
| {{result|warn}} <ref>Test pass, but also encountered {{bz|54321}}</ref>
| {{result|fail}} <ref>{{bz|12345}}</ref>
| {{result|fail}} <ref>{{bz|12345}}</ref>
| <references/>
|-
| [[User:Martix|Martin Holec]]
| {{result|warn||887332}}
| {{result|warn||887339}}
| <references/>
|-
| [[User:jpopelka|Jiri Popelka]]
| {{result|pass}}
| {{result|fail}}
| <references/>
|-
| [[User:jmarko|Juraj Marko]]
| {{result|pass}}
| {{result|warn}} <ref>This test was failing first. After around 5 minutes it was working ok.</ref>
| <references/>
|-
| [[User:jsmith|Jared Smith]]
| {{result|fail}} <ref>The http://rhybar.cz website continued to work, even after I told it to re-probe</ref>
| {{result|fail}} <ref>I got a DNS response, but it did not contain an ANSWER section.  Browsing other websites failed.</ref>
| <references/>
|-
| [[User:Mbriza|Martin Bříza]]
| {{result|pass}}
| {{result|pass}} <ref>Both tests needed to restart the browser (konqueror) to get the actual results. Without restarting it, it was using the old settings.</ref>
| <references/>
|-
| [[User:jpospisi|Jiri Pospisil]]
| {{result|pass}}
| {{result|fail}} <ref>I got a DNS response, but it did not contain an ANSWER section.  Browsing other websites failed.</ref>
| <references/>
| <references/>
|-
|-

Revision as of 17:30, 14 December 2012

Fedora Test Days
Echo-testing-48px.png
Network Test Week (Network Manager + DNSSEC)

Date 2012-12-11
Time all day

Website QA/Fedora_18_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?

Today's installment of Fedora Test Day will focus on Network Manager integration with DNSSEC-trigger.

Who's available

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

Prerequisite for Test Day

  • Installed Fedora 18 Beta with latest updates.
  • DNS server supporting DNSSEC

How to test?

  1. Install: Package-x-generic-16.pngdnssec-trigger
  2. Enable DNSSEC and unbound services: systemctl enable dnssec-triggerd.service; systemctl enable unbound.service
  3. Restart your computer.

Test Cases

Test Results

If you have problems with any of the tests, report a bug to Bugzilla usually for the component dnssec-trigger. 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. Once you have completed the tests, add your results to the Results table below, following the example results from the first line as a template. The first column should be your name with a link to your User page in the Wiki if you have one. For each test case, use the result template to enter your result, as shown in the example result line.

User DNSSEC-trigger DNS-over-SSL References
Sample User
Warning warn
[1]
Fail fail
[2]
  1. Test pass, but also encountered RHBZ #54321
  2. RHBZ #12345
Martin Holec
Warning warn [1]
Warning warn [2]
  1. RHBZ #887332
  2. RHBZ #887339
Jiri Popelka
Pass pass
Fail fail
Juraj Marko
Pass pass
Warning warn
[1]
  1. This test was failing first. After around 5 minutes it was working ok.
Jared Smith
Fail fail
[1]
Fail fail
[2]
  1. The http://rhybar.cz website continued to work, even after I told it to re-probe
  2. I got a DNS response, but it did not contain an ANSWER section. Browsing other websites failed.
Martin Bříza
Pass pass
Pass pass
[1]
  1. Both tests needed to restart the browser (konqueror) to get the actual results. Without restarting it, it was using the old settings.
Jiri Pospisil
Pass pass
Fail fail
[1]
  1. I got a DNS response, but it did not contain an ANSWER section. Browsing other websites failed.