From Fedora Project Wiki

(Test Cases)
(Test Results)
Line 76: Line 76:
| [[User:SampleUser|Sample User]]
| [[User:SampleUser|Sample User]]
| native / tunnel
| native / tunnel / local-only / none
| {{result|none}}  
| {{result|none}}  
| {{result|pass}}
| {{result|pass}}

Revision as of 16:01, 5 December 2012

Fedora Test Days
Network Test Week (Network Manager + IPv6)

Date 2012-12-10
Time all day

Website QA/Fedora_18_test_days
IRC #fedora-test-day (webirc)

Mailing list

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 instalment of Fedora Test Day will focus on Network Manager: IPv6, Bonding, NetworkManager Hotspots, nm-applet, kdeplasma-applets-networkmanagement, Bluetooth

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.
  • IPv6 connectivity on local network
    • Native IPv6 connectivity from your IPS, at work, at school (Eduroam), remote server (dedicated, VPS).
    • Local network router/gateway with IPv6 over IPv4 tunnel setup (6to4, 6in4 or Teredo).
  • Wi-Fi adapter
  • multiple network cards
  • 3G modem
  • Bluetooth adapter and a phone capable of Internet connection sharing over Bluetooth
IPv6 over IPv4 tunnelling
Tunnel ending on localhost is not enough for some testing. Consider using tunnel with endpoint on LAN router/gateway.

How to test?

High level details on how a contributor can get involved. This can include (but not limited to):

  • Areas to target with exploratory testing
  • A list of pre-defined test cases to execute
  • How to report back results

Test Cases

Provide a list of test areas or test cases that you'd like contributors to execute. For other examples, see Category:Test_Cases.

Network Manager features


Desktop integration

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 Bugzilla usually for the component udisks, or 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 result template to enter your result, as shown in the example result line.

User IPv6 connection Sample test 1 Sample test 2 Sample test 3 Sample test 4 References
Sample User native / tunnel / local-only / none
Pass pass
Warning warn
Fail fail
  1. Test pass, but also encountered RHBZ #54321
  2. RHBZ #12345