From Fedora Project Wiki

< QA‎ | Test Days

(update with some commonly used chunks)
Line 7: Line 7:
|}
|}


=== What to test? ===
== What to test? ==


Today's installment of Fedora Test Day will focus on '''<<FIXME>>'''
Today's installment of Fedora Test Day will focus on '''<<FIXME>>'''


=== Who's available ===  
== 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 17: Line 17:
* Quality Assurance - [[User:Tester1|Tester1]] (irc_nick3), [[User:Tester2|Tester2]] (irc_nick4), [[User:Tester3|Tester3]] (irc_nick5)
* Quality Assurance - [[User:Tester1|Tester1]] (irc_nick3), [[User:Tester2|Tester2]] (irc_nick4), [[User:Tester3|Tester3]] (irc_nick5)


=== Prerequisite for Test Day ===  
== Prerequisite for Test Day ==  


List any prerequisite needs for the test event.  A fresh system, virtualized guest, a blank DVD ... a desire to break software?
List any prerequisite needs for the test event.  A fresh system, virtualized guest, a blank DVD ... a desire to break software?
Line 25: Line 25:
* Empty HD IDE/SATA/SCSI
* Empty HD IDE/SATA/SCSI
* Free space on HD
* Free space on HD
* Rawhide Fully updated


=== How to test? ===
Here's a chunk which is commonly used for most Test Days:
 
* An updated [http://fedoraproject.org/get-prerelease {{FedoraVersion|long|next}} pre-release], [[Releases/Rawhide|Rawhide]] (tips on installing Rawhide below), or a [http://alt.fedoraproject.org/pub/alt/nightly-composes/desktop/ nightly live image]
* Your hardware profile uploaded to [http://www.smolts.org Smolt] according to [http://smolts.org/smolt-wiki/Main_Page#Usage these instructions]
 
== How to test? ==


High level details on how a contributor can get involved.  This can include (but not limited to):
High level details on how a contributor can get involved.  This can include (but not limited to):
Line 35: Line 39:
* How to report back results
* How to report back results


=== Test Cases ===
Here's another common chunk:
 
=== '''Update your machine''' ===
 
If you're running {{FedoraVersion|long|next}}, make sure you have all the current updates for it installed, using the update manager. If you want to try Rawhide, 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''' ===
 
Optionally, you may download a non-destructive {{FedoraVersion|long|next}} live image for your architecture. Tips on using a live image are available at [[FedoraLiveCD]]. Live images can be found [http://alt.fedoraproject.org/pub/alt/nightly-composes/desktop/ here].
 
== 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]].


=== 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. Include a link where to report bugs. 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. Include a link where to report bugs. For example:

Revision as of 21:25, 8 April 2010

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

What to test?

Today's installment of Fedora Test Day will focus on <<FIXME>>

Who's available

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

Prerequisite for Test Day

List any prerequisite needs for the test event. A fresh system, virtualized guest, a blank DVD ... a desire to break software?

  • Usb key
  • Usb externally connected HD IDE/SATA
  • Empty HD IDE/SATA/SCSI
  • Free space on HD

Here's a chunk which is commonly used for most Test Days:

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
  • A list of pre-defined test cases to execute
  • How to report back results

Here's another common chunk:

Update your machine

If you're running Fedora 41, make sure you have all the current updates for it installed, using the update manager. If you want to try Rawhide, see the instructions on the Rawhide page on the various ways in which you can install or update to Rawhide. Or:

Live image

Optionally, you may download a non-destructive Fedora 41 live image for your architecture. Tips on using a live image are available at FedoraLiveCD. Live images can be found here.

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.

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. Include a link where to report bugs. For example:

Please report all bugs into Bugzilla against the FIXME component.

User Smolt Profile Sample test 1 Sample test 2 Sample test 3 Sample test 4 References
Sample User HW
none
Pass pass
Warning warn
[1]
Fail fail
[2]
  1. Test pass, but also encountered RHBZ #54321
  2. RHBZ #12345