From Fedora Project Wiki

(tests description and link →‎X Window System)
(new links →‎Single mode)
Line 71: Line 71:
==== Single mode ====
==== Single mode ====


Estimated time: ''10 minutes''
These tests should be performed in single mode. We recommend reading the description of both tests and performing these in sequence - to refrain more reboots.
 
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.


{| style="width:100%"
{| style="width:100%"
!style="width:30%"|TestCase
!style="width:15%"|Testcase
!style="width:50%"| Description
!style="width:75%"|Description
!style="width:20%"| Extra Requirements
!style="width:10%"|ETA
|-   
|-   
| [[QA:Testcase_Power_Management_Tuned]]   
| [[Test_Day:2009-10-22/Testcase:tuned|tuned]]   
| Measuring differencies with and without tuned
| CPU states and frequencies when ''tuning'' daemon enabled
| ''?''
| 7 minutes
|-
|-
| [[QA:Testcase_Power_Management_init_1]]  
| [[Test_Day:2009-10-22/Testcase:basic|basic]]  
| Some measures in lowest runlevel. FTP working, copying of files, bzipping archive
| Stress situations (BZIP2 compression, disk copying, vsftpd test)
| ''?''
| 2 minutes
|}
|}



Revision as of 13:43, 15 October 2009

DATE WHEN WHERE
2009-10-22 From 12:00 to 21:00 UTC (8am -> 5pm EDT) #fedora-test-day (webirc)
Warning.png
Under construction
The site is still under construction. Anything can change before the testday.

Purpose of this test

Warning.png
TODO
Some text here. ;)

Who's available

The following cast of characters will be available testing, workarounds, bug fixes, general discussion ...

Prerequisite

Warning.png
TODO
Upload new RPM, update its name, what about signing it?
  • Rawhide (development version of Fedora) with graphical environment
  • SELinux disabled
  • 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
  • Kernel debugging info:
    • Use debuginfo-install kernel or install it manually. (In case of manual installation you have to enable debug repository in /etc/yum.repos.d/fedora-rawhide.repo.)
    • Versions of kernel and kernel-debuginfo must be the same. Please check it with:
      • uname -a
      • rpm -q kernel-debuginfo
  • 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)
Important.png
Privileges
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

These tests should be performed on all systems in X11 environment.

Testcase Description ETA
personal Typical use of computer (do whatever you are doing usually). CPU states and frequencies. 10 minutes
scomes Ticks, syscall count, read/written bytes when performing some specific tasks. 1 minute

Single mode

These tests should be performed in single mode. We recommend reading the description of both tests and performing these in sequence - to refrain more reboots.

Testcase Description ETA
tuned CPU states and frequencies when tuning daemon enabled 7 minutes
basic Stress situations (BZIP2 compression, disk copying, vsftpd test) 2 minutes

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

Warning.png
TODO
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%
2.14 Ghz 0.0%
1.87 Ghz 0.0%
1.60 Ghz 98.5%
Wakeups-from-idle per second : 99.5 interval: 30.0s

PASS FAIL [1]

2.40 Ghz 1.5%
2.14 Ghz 0.0%
1.87 Ghz 0.0%
1.60 Ghz 98.5%
Wakeups-from-idle per second : 99.5 interval: 30.0s

PASS PASS
  1. See RHBZ #12345