From Fedora Project Wiki

No edit summary
Line 129: Line 129:
| IN PROGRESS
| IN PROGRESS
| IN PROGRESS
| IN PROGRESS
| IN PROGRESS
| FAIL <ref>See {{bz|520616}}</ref>
| IN PROGRESS
| IN PROGRESS
| <references/>
| <references/>

Revision as of 13:18, 1 September 2009

DATE TIME WHERE
Sectool Fit&Finish From 12:00 to 21:00 UTC (8am -> 5pm EDT) #fedora-test-day (webirc)

What to test?

Today's installment of Fedora Test Day / Fit & Finish will focus on Sectool.

Who's available

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

  • Development - Maros Barabas (nick xBarry), Jakub Hrozek (nick jhrozek)
  • Quality Assurance - Eduard Benes (nick ebenes), Miroslav Vadkerty (nick mvadkert)

Prerequisite for Test Day

  • Any sectool version >= 0.9.4 on Fedora 11 or Rawhide system. (the more different testing environment we get, the better)
  • Install sectool by running following commands:
 rpm -Uvh http://mbarabas.fedorapeople.org/sectool-0.9.4-2.fc11.i586.rpm
 rpm -Uvh http://mbarabas.fedorapeople.org/sectool-gui-0.9.4-2.fc11.i586.rpm


How to test?

High level details on how a contributor can get involved. This can include (but not limited to):

  • Areas to target with exploratory testing: GUI, DBus, Sectool Tests under different test env.
  • A list of pre-defined test cases to execute: see section 'Test Cases'. Additonally you can follow links in the 'Tests Results' table header.
  • How to report back results: bugzilla, table in section 'Test Results'

For additional info see: https://fedoraproject.org/wiki/Features/Sectool Sectool homepage: https://fedorahosted.org/sectool/

Knonwn Issues

Sectool has missing SELinux policy - See RHBZ #520577

Test Cases

See 'How To Test' section on the Feature page: https://fedoraproject.org/wiki/Features/Sectool#How_To_Test Additonal ideas:

Test Results

Test results table for individual test cases (direct links in the first row).

User Smolt Profile Sanity testing Running the tests Running a level Display filters Test auto action Diff and sending a mail Overriding levels Logging DBus testing GUI testing References
User:FasUser HW FAIL [1] PASS PASS PASS PASS PASS PASS PASS PASS PASS
  1. See RHBZ #12345
User:Liam f12 rawhide PASS PASS FAIL [1] PASS PASS PASS PASS PASS PASS PASS
  1. See RHBZ #520557
User:Rhe f12 rawhide PASS PASS FAIL [1] PASS PASS PASS PASS PASS FAIL [2] PASS
  1. See RHBZ #520557
  2. See RHBZ #520579
User:mvadkert HW FAIL [1] FAIL [2] IN PROGRESS IN PROGRESS IN PROGRESS IN PROGRESS IN PROGRESS IN PROGRESS FAIL [3] IN PROGRESS
  1. See RHBZ #520588
  2. See RHBZ #520592
  3. See RHBZ #520616
User:ebenes HW FAIL [1] [2] FAIL [3] IN PROGRESS IN PROGRESS IN PROGRESS IN PROGRESS IN PROGRESS IN PROGRESS IN PROGRESS IN PROGRESS
  1. See RHBZ #520588
  2. See RHBZ #520591
  3. See RHBZ #520592