Test Day:2009-08-13 NetworkManager

What to test?
Today's instalment of Fedora Test Day will focus on Tools/NetworkManager, including:
 * Features/MoreNetworkManagerMobileBroadband
 * Features/NetworkManagerIPv6
 * Features/NetworkManagerSystemConnections

If you come to this page after the test day is completed, your testing is still valuable, and you can use the information on this page to test with your system and provide feedback.

Who's available
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...
 * Development - Dan Williams
 * Quality Assurance - Adam Williamson

What's needed to test

 * A system with some kind of network connection
 * Rawhide (tips on installing Rawhide below), or the live CD available for this test day (again see below).
 * Your hardware profile uploaded to Smolt according to these instructions

Update your machine
See the instructions on the Rawhide page on the various ways in which you can install or update to Rawhide. Or:

Live Image
Optionally, you may download a non-destructive rawhide live image for your architecture. Tips on using a live image are available at FedoraLiveCD.

Test
Follow each of these test cases that are possible with the hardware you have available:


 * QA:Testcase_NetworkManager_celldata (requirements: a cellular data (3G) modem)
 * QA:Testcase_NetworkManager_ipv6 (requirements: a functional IPv6 network)
 * QA:Testcase_NetworkManager_assume (requirements: a functional wired ethernet connection)
 * QA:Testcase_NetworkManager_bt_pan (requirements: a device capable of acting as a Bluetooth PAN server - many cellphones)

Report your results
If you have problems with any of the tests, report a bug to Bugzilla usually for the component NetworkManager. If you are unsure about exactly how to file the report, 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 your Smolt hardware profile (see above for a link with instructions on submitting your hardware profile to Smolt). For each test case, if your system worked correctly, simply enter the word PASS. If you had trouble, enter the word FAIL, with a footnote indicator, and put a link to the bug report in the References column (as in the example line). For tests you could not perform, enter a dash.

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. For example: