From Fedora Project Wiki

(Initial version)
 
Line 3: Line 3:
 
| DATE || TIME || WHERE
 
| DATE || TIME || WHERE
 
|-
 
|-
| '''Sectool'' || From ''12:00'' to ''21:00'' UTC (8am -> 5pm EDT) || [irc://irc.freenode.net/fedora-test-day #fedora-test-day] ([http://webchat.freenode.net/?channels=fedora-test-day webirc])
+
| '''Sectool''' Fit&Finish || From ''12:00'' to ''21:00'' UTC (8am -> 5pm EDT) || [irc://irc.freenode.net/fedora-test-day #fedora-test-day] ([http://webchat.freenode.net/?channels=fedora-test-day webirc])
 
|-
 
|-
 
|}
 
|}
Line 9: Line 9:
 
=== What to test? ===
 
=== What to test? ===
  
Today's installment of Fedora Test Day will focus on '''Sectool'''
+
Today's installment of Fedora Test Day / Fit & Finish will focus on '''Sectool'''.
  
 
=== Who's available ===  
 
=== Who's available ===  
Line 33: Line 33:
  
 
* Areas to target with exploratory testing: GUI, DBus, Sectool Tests under different test env.
 
* Areas to target with exploratory testing: GUI, DBus, Sectool Tests under different test env.
* A list of pre-defined test cases to execute: see following section.
+
* 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'
 
* How to report back results: bugzilla, table in section 'Test Results'
  
Line 42: Line 42:
  
 
See 'How To Test' section on the Feature page: https://fedoraproject.org/wiki/Features/Sectool#How_To_Test
 
See 'How To Test' section on the Feature page: https://fedoraproject.org/wiki/Features/Sectool#How_To_Test
 +
Additonal ideas:
 +
* [https://fedorahosted.org/sectool/wiki/BashTestTutorial Create your own sectool test in bash]
 +
* [https://fedorahosted.org/sectool/wiki/PythonTestTutorial Create your own sectool test in python]
  
 
=== Test Results ===
 
=== 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:
 +
-->
  
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:
+
Test results table for individual test cases (direct links in the first row).
  
 
{|
 
{|
Line 64: Line 70:
 
|-
 
|-
 
| [[User:FasUser]]  
 
| [[User:FasUser]]  
 +
| [http://www.smolts.org/client/show/pub_84465125-1350-4f83-87b9-5f16f7430eb8 HW]
 +
| FAIL <ref>See {{bz|12345}}</ref>
 +
| PASS
 +
| PASS
 +
| PASS
 +
| PASS
 +
| PASS
 +
| PASS
 +
| PASS
 +
| PASS
 +
| PASS
 +
| <references/>
 +
|-
 +
|-
 +
| [[User:AnotherTestUser]]
 
| [http://www.smolts.org/client/show/pub_84465125-1350-4f83-87b9-5f16f7430eb8 HW]
 
| [http://www.smolts.org/client/show/pub_84465125-1350-4f83-87b9-5f16f7430eb8 HW]
 
| FAIL <ref>See {{bz|12345}}</ref>
 
| FAIL <ref>See {{bz|12345}}</ref>
Line 78: Line 99:
 
|-
 
|-
 
|}
 
|}
 +
  
 
[[Category:Test Days]]
 
[[Category:Test Days]]

Revision as of 16:51, 24 August 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 ...

Prerequisite for Test Day

  • F12 system with sectool.

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/

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:AnotherTestUser HW FAIL [1] PASS PASS PASS PASS PASS PASS PASS PASS PASS
  1. See RHBZ #12345