| DATE | WHEN | WHERE |
| 2009-10-22 | From 12:00 to 21:00 UTC (8am -> 5pm EDT) | #fedora-test-day (webirc) |
The site is still under construction. Anything can change before the testday.
Purpose of this test
Some text here. ;)
Who's available
The following cast of characters will be available testing, workarounds, bug fixes, general discussion ...
- Development - Phil Knirsch, Marcela Maslanova (marcela on irc), Petr Lautrbach, Jiri Skala (skalnik on irc)
- Quality Assurance - David Pravec (dpravec), Jan Scotka
Prerequisite
Upload new RPM, update its name, what about signing it?
- Rawhide - development version of Fedora
- Internet connection
- The special-purpose Testday RPM package which includes necessary dependencies and provides all testing scripts.
- Download and install with:
yum --nogpgcheck localinstall testday-pm-0.1-2.fc12.noarch.rpm
- Download and install with:
- Kernel debugging info:
- Use
debuginfo-install kernelor install it manually. (In case of manual installation you have to enable debug repository in/etc/yum.repos.d/fedora-rawhide.repo.) - Versions of
kernelandkernel-debuginfomust be the same. Please check it with:uname -arpm -q kernel-debuginfo
- Use
- Upload your hardware to Smolt according to these instructions.
Running the tests
Update your machine
See the instructions on the Rawhide page on the various ways in which you can install or update to Rawhide.
Tests
The test cases are split into test groups. Some of the tests are a bit time-consuming. Please perform as many tests as possible. If you aren't able to run them all, please remember that the tests in each table are sort by importance in descending order.
You don't have to download any special scripts for each test. Our Testday package provides following commands:
testday-run-testname(performing tests)testday-pack-results(packing results of all tests in .tag.gz file)
Please perform all tests as a regular user. Some tests require superuser permission. In these cases you will be informed by testing script.
X Window System
Create separate page for each test.
Estimated time: 12 minutes
These tests should be performed on all systems with X11 (desktop, laptops).
| Testcase | Description |
|---|---|
| Test_Day:2009-10-22/Testcase:personal | Typical use of computer (Do whatever you are doing usually) |
| QA:Testcase_Power_Management_scomes | Measuring and collecting data with scomes tool
|
Single mode
Estimated time: 10 minutes
These tests should be performed on all systems (desktop, laptop, servers). As you will have to reboot into single mode, install all required packages before. We recommend running the tests in sequence to refrain more reboots.
| TestCase | Description | Extra Requirements |
|---|---|---|
| QA:Testcase_Power_Management_Tuned | Measuring differencies with and without tuned | ? |
| QA:Testcase_Power_Management_init_1 | Some measures in lowest runlevel. FTP working, copying of files, bzipping archive | ? |
Laptops
Estimated time: 20-35 minutes
Following tests are intended only for laptops. If you don't have a laptop, don't perform these tests because there is no easy way how to measure your system consumption. You need to charge your battery before.
| TestCase | Description | Extra Requirements |
|---|---|---|
| QA:Testcase_Power_Management_bltk | 3 workloads (Idle, OpenOffice, reader) measure power consumption of simulated reproducable load | OpenOffice is required during bltk installation, Firefox |
| QA:Testcase_Power_Management_tuned-adm | Measuring tuned profiles with bltk
|
tuned-adm, bltk |
Test Results
Hmm. We have to change this.
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 | PM Personal test | PM scomes test | PM tuned test | PM init1 test | PM BLTK test | PM tuned-adm test | References |
|---|---|---|---|---|---|---|---|---|
| User:FasUser | HW |
2.40 Ghz 1.5% |
PASS | FAIL [1] |
2.40 Ghz 1.5% |
PASS | PASS |