Latest revision |
Your text |
Line 83: |
Line 83: |
|
| |
|
| With your system installed, you are ready to move on to testing. Good luck! | | With your system installed, you are ready to move on to testing. Good luck! |
|
| |
| ===== Updating NetworkManager Packages =====
| |
|
| |
| Once your system is installed, you'll need to install the latest NetworkManager packages built for testing. Instructions for installing the latest packages are listed below.
| |
|
| |
| 1 Create a yum repo for Fedora Test Day packages ...
| |
| <pre>$ cat <<EOF>/etc/yum.repos.d/fedora-test-day.repo
| |
| [fedora-test-day]
| |
| name=fedora-test-day
| |
| baseurl=http://jlaska.fedorapeople.org/fedora-test-day/\$releasever/\$basearch
| |
| enabled=0
| |
| gpgcheck=0
| |
| EOF</pre>
| |
|
| |
| 2 Upgrade to the Test Day packages ... <pre>$ yum --enablerepo=fedora-test-day --enablerepo=updates* update NetworkManager*</pre>
| |
|
| |
| 3 Restart the NetworkManager service <pre>$ /sbin/service NetworkManager restart</pre>
| |
|
| |
| ===== Forcing Anaconda to Fail =====
| |
|
| |
| While errors (referred to as tracebacks) during installation are not uncommon during the development cycle. If you need to force the installation program to fail in order to test the SaveToBugzilla functionality, the easiest way is to boot with the following command-line option:
| |
|
| |
| <pre>updates=http://jlaska.fedorapeople.org/traceback.img</pre>
| |
|
| |
| This will cause the installation program to fail after clicking "Next" for the first time. This will present an error dialog which you can use to test [[Anaconda/Features/SaveToBugzilla|SaveToBugzilla]]
| |
|
| |
|
| ==== Exploratory Testing ==== | | ==== Exploratory Testing ==== |
Line 126: |
Line 101: |
| ** Exercise different wireless security settings | | ** Exercise different wireless security settings |
| ** VPN over a shared connection? | | ** VPN over a shared connection? |
|
| |
| * Anaconda SaveToBugzilla
| |
| ** Invalid data (username, password, empty description, really long description)
| |
| ** Valid data, repeat several times
| |
|
| |
|
| ==== Targeted Testing ==== | | ==== Targeted Testing ==== |
Line 147: |
Line 118: |
|
| |
|
| Come join us on #fedora-qa, ask questions, propose changes, and share your issues. | | Come join us on #fedora-qa, ask questions, propose changes, and share your issues. |
|
| |
| ==== Bug Filing Tips ====
| |
|
| |
| When filing ''NetworkManager'' bugs, please include the following information in the bug report.
| |
|
| |
| # <code>iwconfig</code> output for the card
| |
| # <code>/usr/bin/nm-tool</code> output (mask AP addresses and your MAC if you like),
| |
| # <code>iwlist scan</code> output (mask AP addresses again if you like)
| |
|
| |
| For assistance filing ''installation (anaconda)'' bug reports, refer to [[How to debug installation problems]].
| |
|
| |
|
| === Known Issues === | | === Known Issues === |
Line 162: |
Line 123: |
| Both features have been available for testing already through rawhide. As a result, there is a list of bugs already filed for each area. Before you file a new bug, please refer to the following before filing a new bug: | | Both features have been available for testing already through rawhide. As a result, there is a list of bugs already filed for each area. Before you file a new bug, please refer to the following before filing a new bug: |
|
| |
|
| * NetworkManager [http://tinyurl.com/6zr48v known issues] | | * FIXME |
| * Anaconda [http://tinyurl.com/5gm9qg known issues]
| | {{admon/important|FIXME|Provide known issues links}} |
| | |
| ** Bug is filed, but no traceback attached, and no 0x0HASH in the whiteboard (see [[rhbug:461148]])
| |
| ** No user feedback provided after submitting bug
| |
| ** The mouse cursor turns into an hourglass, and never turns back to a pointer
| |
| | |
| [[Category:Fedora 10 Test Days]]
| |