No edit summary |
No edit summary |
||
Line 12: | Line 12: | ||
== What to test? == | |||
=== For "Extended tuned" === | |||
* yum install tuned | * yum install tuned | ||
* service tuned start | * service tuned start | ||
Line 20: | Line 20: | ||
* If ktune is enabled check if the system settings for the current profile are being applied and restored when stopping the service | * If ktune is enabled check if the system settings for the current profile are being applied and restored when stopping the service | ||
=== For "System tuning configuration and profiles" === | |||
* Run the new system tuning tool and list the different available profiles using: | * Run the new system tuning tool and list the different available profiles using: | ||
** tuned-adm list | ** tuned-adm list | ||
Line 27: | Line 27: | ||
** tuned-adm modes default | ** tuned-adm modes default | ||
** tuned-adm modes throughput-performance | ** tuned-adm modes throughput-performance | ||
=== For "New tool to measure improvements to system configuration changes or application changes" === | |||
* yum install tuned-utils | * yum install tuned-utils | ||
* run scomes | * run scomes | ||
Line 35: | Line 35: | ||
== Who's available == | |||
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ... | The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ... | ||
Line 42: | Line 43: | ||
== Prerequisite for Test Day == | |||
Line 50: | Line 51: | ||
== How to test? == | |||
=== Update your machine === | |||
See the instructions on the [[Releases/Rawhide|Rawhide]] page on the various ways in which you can install or update to Rawhide. Or: | See the instructions on the [[Releases/Rawhide|Rawhide]] page on the various ways in which you can install or update to Rawhide. Or: | ||
=== Live Image === | |||
(live CD is tested. The results and suitability will be explained here) | (live CD is tested. The results and suitability will be explained here) | ||
Line 64: | Line 65: | ||
* How to report back results | * 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]]. | <!-- Provide a list of test areas or test cases that you'd like contributors to execute. For other examples, see [[:Category:Test_Cases]]. | ||
Line 112: | Line 113: | ||
|} | |} | ||
=== Test Results === | |||
Revision as of 09:18, 23 September 2009
DATE | WHEN | WHERE |
2009-10-22 | From 12:00 to 21:00 UTC (8am -> 5pm EDT) | #fedora-test-day (webirc) |
WARNING! The site is still under construction
What to test?
For "Extended tuned"
- yum install tuned
- service tuned start
- cpu, disk and net devices should adapt to usage (monitor using strace e.g.)**
- If ktune is enabled check if the system settings for the current profile are being applied and restored when stopping the service
For "System tuning configuration and profiles"
- Run the new system tuning tool and list the different available profiles using:
- tuned-adm list
- Run the new system tuning tool and select one of the profiles. Restart the machine afterwards and make sure the profile is being used at startup
- tuned-adm modes laptop-battery-powersave
- tuned-adm modes default
- tuned-adm modes throughput-performance
For "New tool to measure improvements to system configuration changes or application changes"
- yum install tuned-utils
- run scomes
- change system settings
- run scomes again
- compare restults
Who's available
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...
- Development - Phil Knirsch, Marcela Maslanova, Petr Lautrbach, Jiri Skala (skalnik on irc)
- Quality Assurance - David Pravec (dpravec), Jan Scotka
Prerequisite for Test Day
- A system with some kind of network connection
- Rawhide (tips on installing Rawhide below - the live CD is tested to - suitability for this test day).
- 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:
Live Image
(live CD is tested. The results and suitability will be explained here)
Optionally, you may download a non-destructive rawhide live image for your architecture. Tips on using a live image are available at FedoraLiveCD.
- Areas to target with exploratory testing
- How to report back results
Test Cases
TestCase | Description | Extra Requirements |
---|---|---|
QA:Testcase_Power_Management_tuned-adm | ? | ? |
QA:Testcase_Power_Management_personal | ? | ? |
QA:Testcase_Power_Management_Tuned | ? | ? |
QA:Testcase_Power_Management_init_1 | ? | ? |
QA:Testcase_Power_Management_bltk | ? | ? |
QA:Testcase_NetworkManager_celldata | ? | a cellular data (3G) modem |
QA:Testcase_NetworkManager_ipv6 | ? | a functional IPv6 network |
QA:Testcase_NetworkManager_assume | ? | a functional wired ethernet connection |
QA:Testcase_NetworkManager_bt_pan | ? | a device capable of acting as a Bluetooth PAN server - many cellphones |
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. For example:
User | Smolt Profile | Sample test 1 | Sample test 2 | Sample test 3 | Sample test 4 | References |
---|---|---|---|---|---|---|
User:FasUser | HW | PASS | PASS | FAIL [1] | PASS |