From Fedora Project Wiki

m (Updated category)
 
(20 intermediate revisions by 12 users not shown)
Line 47: Line 47:
* [[How to setup tunnel broker via Hurricane Electric]]
* [[How to setup tunnel broker via Hurricane Electric]]
* [[How to setup a tunnel broker via Sixxs.net]]
* [[How to setup a tunnel broker via Sixxs.net]]
* [[How to setup a 6to4 tunnel using anycast (RFC 3056)]]


== Test Cases ==
== Test Cases ==
Line 55: Line 56:
*# ifconfig your interface to make sure your IPv6 address are setup correctly.
*# ifconfig your interface to make sure your IPv6 address are setup correctly.
*# ping various external ipv6 websites such as <code>ipv6.google.com</code> to see if you can download the web content through your ipv6 connection
*# ping various external ipv6 websites such as <code>ipv6.google.com</code> to see if you can download the web content through your ipv6 connection
*# Run test program here: http://test-ipv6.com
* Run http://test-ipv6.com
* [[QA:Testcase_NetworkManager_ipv6]] - To test IPv6 on Network Manager, please see following link for instruction:
* [[QA:Testcase_NetworkManager_ipv6]] - To test IPv6 on Network Manager, please see following link for instruction:
* [[QA:Testcase_NFS_IPv6]] - To test IPv6 on NFS filesystem, please see following link for instruction:
* [[QA:Testcase_NFS_IPv6]] - To test IPv6 on NFS filesystem, please see following link for instruction:
Line 90: Line 91:
| [[User:Dramsey|David Ramsey]]
| [[User:Dramsey|David Ramsey]]
| [[QA:Testcase_NetworkManager_ipv6]]
| [[QA:Testcase_NetworkManager_ipv6]]
| {{result|inprogress}}
| {{result|pass}}
| <references/>
| <references/>
|-
|-
| [[User:Dramsey|David Ramsey]]
| [[User:Dramsey|David Ramsey]]
| [[QA:Testcase_IPv6_printing]]
| [[QA:Testcase_IPv6_printing]]
| {{result|inprogress}}
| {{result|pass}}
| <references/>
| <references/>
|-
|-
| [[User:Dramsey|David Ramsey]]
| [[User:Dramsey|David Ramsey]]
| [[QA:Testcase_NFS_IPv6]]
| [[QA:Testcase_NFS_IPv6]]
| {{result|inprogress}}
| {{result|pass}}
| <references/>
| <references/>
|-
|-
Line 121: Line 122:
| [[QA:Testcase_various_IPv6_commands]]
| [[QA:Testcase_various_IPv6_commands]]
| {{result|pass}}
| {{result|pass}}
| <references/>
|-
| [[User:lintweaker|Jurgen Kramer]]
| [[QA:Testcase_various_IPv6_commands]]
| {{result|pass}}
| <references/>
|-
| [[User:Lintweaker|Jurgen Kramer]]
| [[QA:Testcase_NFS_IPv6]]
| {{result|pass}}
| <references/>
|-
| [[User:Evillagr|Eduardo Villagrán]]
| [[QA:Testcase_various_IPv6_commands]]
| {{result|pass}}
| <references/>
|-
|-
| [[User:Evillagr|Eduardo Villagrán]]
| [[QA:Testcase_NFS_IPv6]]
| {{result|pass}}
| <references/>
| <references/>
| [[User:lintweaker|Jurgen Kramer]]
|-
| [[User:jbastian|Jeff Bastian]]
| [[QA:Testcase_NetworkManager_ipv6]]
| {{result|pass}}
| <references/>
|-
| [[User:jbastian|Jeff Bastian]]
| [[QA:Testcase_IPv6_printing]]
| {{result|pass}}
| <references/>
|-
| [[User:ricky|Ricky Zhou]]
| [[QA:Testcase_NetworkManager_ipv6]]
| {{result|pass}}
| <references/>
|-
| [[User:ricky|Ricky Zhou]]
| [[QA:Testcase_various_IPv6_commands]]
| {{result|pass}}
| <references/>
|-
| [[User:lmacken|Luke Macken]]
| [[QA:Testcase_various_IPv6_commands]]
| {{result|pass}}
| <references/>
|-
| [[User:fbl|Flavio Leitner]]
| [[QA:Testcase_various_IPv6_commands]]
| [[QA:Testcase_various_IPv6_commands]]
| {{result|pass}}
| {{result|pass}}
| <references/>
| <references/>
|-
|}
|}


=== Problems Identified ===
=== Problems Identified ===
Use the following table to record tests that highlight defects or otherwise inconsistent behaviors.
Use the following table to record tests that highlight defects or otherwise inconsistent behaviours.


{|
{|
Line 138: Line 185:
! References
! References
|-
|-
| [[User:SampleUser|Sample User]]
| [[User:Lintweaker|Jurgen Kramer]]
| [[QA:Testcase_NetworkManager_ipv6]]
| [[QA:Testcase_NetworkManager_ipv6]]
| {{result|fail|12345|54321}}
| {{result|fail|DHCPv6 blocked by firewall|650615}}
| <references/>
|-
|[[User:Tuju|Tuju]]
|
| CUPS queue discovery doesn't work.
| [https://bugzilla.redhat.com/show_bug.cgi?id=611213 bug 611213]
|-
| [[User:Rombobeorn|Björn Persson]]
| [[QA:Testcase_various_IPv6_commands]]
| {{result|fail|ping6 tries to ping an IPv4 address when a domain name has both IPv4 and IPv6 addresses.|711827}}
| <references/>
|-
| [[User:jbastian|Jeff Bastian]]
| [[QA:Testcase_NFS_IPv6]]
| {{result|fail|cannot automount NFSv4 over IPv6|711844}}
| <references/>
| <references/>
|-
|-
| [[User:Adamwill|Adam Williamson]]
|
| Bip (IRC proxy) behaves badly when system has a global IPv6 address but is not capable of IPv6 DNS resolution: doesn't fall back to IPv4 and fails to connect to anything. Will report upstream
| <references/>
|}
|}




[[Category:Test Days]]
[[Category:Fedora 16 Test Days]]
[http://www.p90xworkoutfree.com/  p90x]
[http://www.suprashoesfra.com/  Supra For Sale]

Latest revision as of 19:10, 30 June 2011

Fedora Test Days
World IPv6 Test Day

Date June-08-2011
Time all day

Website http://isoc.org/wp/worldipv6day/
IRC #fedora-test-day (webirc)
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.

What to test?[edit]

Since June 8, 2011 is the World IPv6 Day, today's installment of Fedora Test Day will focus on IPv6 testing.

Who's available[edit]

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

Prerequisite for Test Day[edit]

  • An up-to-date Fedora 15 system with IPv6 enabled
  • An internet connection via an ISP who supports IPv6 and an IPv6 address from that ISP, or an IPv6 tunnel broker (refer to #Prepare an IPv6 connection)

How to test?[edit]

Update your machine[edit]

If you're running Fedora 15, make sure you have all the current updates for it installed, using the update manager.

Live image[edit]

Optionally, you may download a non-destructive live image for your architecture. Tips on using a live image are available at FedoraLiveCD. Live images can be downloaded here.

Prepare an IPv6 connection[edit]

Check if your ISP offers native IPv6 connectivity. If so, follow the instructions provided by your ISP.

Otherwise, you will need to setup a tunnel broker following one of the suggestions below.

Test Cases[edit]

The following list of tests are simply suggested test areas. Participants are encouraged to test and provide feedback for areas not listed below.

  • Exploratory Testing...
    1. ifconfig your interface to make sure your IPv6 address are setup correctly.
    2. ping various external ipv6 websites such as ipv6.google.com to see if you can download the web content through your ipv6 connection
  • Run http://test-ipv6.com
  • QA:Testcase_NetworkManager_ipv6 - To test IPv6 on Network Manager, please see following link for instruction:
  • QA:Testcase_NFS_IPv6 - To test IPv6 on NFS filesystem, please see following link for instruction:
  • QA:Testcase_IPv6_printing - 1. setup the system using ipv6 address, 2. setup printer's ipv6 address via printer instructions, 3. setup the printer queue as if the the printer uses ipv6 address.
  • QA:Testcase_various_IPv6_commands - Test various command-line IPv6 utilities

Test Results[edit]

If you have problems with any of the tests, try and report a bug. Most bugs in this event should be reported to Fedora Bugzilla. You will need a bugzilla account to report bugs, but creating one is easy, and we will help you do this if you ask in IRC.

If you are not sure of the appropriate component, please check in IRC before filing, there are many possibilities. 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 appropriate table below, following the example results from the first line as a template. The results use the wiki template {{result}}. For guidance an syntax, refer to Template:Result.

Things that work[edit]

Use the following table to record tests successfully completed.

Tester Test Performed / Description Result References
Sample User QA:Testcase_NetworkManager_ipv6
Pass pass
Athmane Madjoudj QA:Testcase_various_IPv6_commands
Pass pass
David Ramsey QA:Testcase_NetworkManager_ipv6
Pass pass
David Ramsey QA:Testcase_IPv6_printing
Pass pass
David Ramsey QA:Testcase_NFS_IPv6
Pass pass
David Ramsey QA:Testcase_various_IPv6_commands
Pass pass
Raina Otoni QA:Testcase_NetworkManager_ipv6
Pass pass
Raina Otoni QA:Testcase_NFS_IPv6
Pass pass
Raina Otoni QA:Testcase_various_IPv6_commands
Pass pass
Jurgen Kramer QA:Testcase_various_IPv6_commands
Pass pass
Jurgen Kramer QA:Testcase_NFS_IPv6
Pass pass
Eduardo Villagrán QA:Testcase_various_IPv6_commands
Pass pass
Eduardo Villagrán QA:Testcase_NFS_IPv6
Pass pass
Jeff Bastian QA:Testcase_NetworkManager_ipv6
Pass pass
Jeff Bastian QA:Testcase_IPv6_printing
Pass pass
Ricky Zhou QA:Testcase_NetworkManager_ipv6
Pass pass
Ricky Zhou QA:Testcase_various_IPv6_commands
Pass pass
Luke Macken QA:Testcase_various_IPv6_commands
Pass pass
Flavio Leitner QA:Testcase_various_IPv6_commands
Pass pass

Problems Identified[edit]

Use the following table to record tests that highlight defects or otherwise inconsistent behaviours.

Tester Test Performed / Description Result References
Jurgen Kramer QA:Testcase_NetworkManager_ipv6
Fail fail DHCPv6 blocked by firewall [1]
  1. RHBZ #650615
Tuju CUPS queue discovery doesn't work. bug 611213
Björn Persson QA:Testcase_various_IPv6_commands
Fail fail ping6 tries to ping an IPv4 address when a domain name has both IPv4 and IPv6 addresses. [1]
  1. RHBZ #711827
Jeff Bastian QA:Testcase_NFS_IPv6
Fail fail cannot automount NFSv4 over IPv6 [1]
  1. RHBZ #711844
Adam Williamson Bip (IRC proxy) behaves badly when system has a global IPv6 address but is not capable of IPv6 DNS resolution: doesn't fall back to IPv4 and fails to connect to anything. Will report upstream