|Thu August 13, 2009||From 12:00 to 24:00 UTC (8am -> 8pm EDT)||#fedora-qa (webirc)|
What to test?
Today's instalment of Fedora Test Day will focus on Tools/NetworkManager, including:
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.
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...
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
How to test?
Update your machine
See the instructions on the Rawhide page on the various ways in which you can install or update to Rawhide. Or:
Optionally, you may download a non-destructive rawhide live image for your architecture. Tips on using a live image are available at FedoraLiveCD.
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.
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:
|User||Smolt Profile||Cellular data||IPv6||Connection assuming||Bluetooth PAN||References|
|User:Rhe||HW||N/A||N/A||FAIL ||N/A|| |
|User:hpt||[N/A]||N/A||N/A||FAIL ||N/A|| |
|User:czhang||smoltSendProfile return "invalid argument to setopt" error||N/A||FAIL ||FAIL ||FAIL (no "Access the internet using your mobile phone" checkbox when pairing with Nokia N81, a Windows-Mobile phone needed.|
|User:Scop||Could not send off the live CD ||FAIL ||N/A||FAIL ||FAIL (no "Access the internet using your mobile phone" checkbox when pairing with Nokia E71)|
|User:guaneryu||smoltSendProfile failed on LiveCD ||FAIL ||FAIL ||FAIL  ||N/A|
|User:hdong||smoltSendProfile retrun "invalid arguments to setopt"||FAIL ||FAIL ||FAIL ||N/A|
|User:vbenes||smoltSendProfile return "invalid argument to setopt" error ||N/A||FAIL ||FAIL  ||N/A|
|Michal Nowak||smoltSendProfile return "invalid argument to setopt" error||N/A||N/A||FAIL RHBZ #517229||N/A|
|User:jkoten||smoltSendProfile return "invalid argument to setopt" error ||N/A||FAIL ||PASS ||N/A|
|User:zmc||smoltSendProfile return "invalid argument to setopt" error ||N/A||N/A||FAIL ||N/A|
|User:jlaska||||FAIL ||N/A||PASS ||N/A|
|User:Jrowens||||N/A||FAIL ||FAIL ||N/A|
|User:lixiao||smoltSendProfile return "invalid argument to setopt" ||FAIL ||FAIL ||FAIL  ||N/A|
|User:fluo||N/A||FAIL ||FAIL ||FAIL ||N/A|
|User:apetz||N/A||PASS||N/A||N/A||FAIL (no "Access the internet using your mobile phone" checkbox when pairing with SE K610i)||Vodaphone E3730 HSDPA Express Card|