From Fedora Project Wiki

m
(Drop direct Test Days category membership)
 
(3 intermediate revisions by 2 users not shown)
Line 14: Line 14:
 
== What to test? ==
 
== What to test? ==
  
Today's instalment of Fedora Test Day will focus on '''<<FIXME>>'''
+
Today's instalment of Fedora Test Day will focus on '''BoxGrinder Build''' and '''Fedora on EC2'''.
  
== Who's available ==
+
Detailed information about tests for selected feature is available on features page listed below.
  
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...
+
== BoxGrinder Build ==
* Development - [[User:Goldmann|Marek Goldmann]] (mgoldmann)
 
* Quality Assurance - [[User:Tester1|Tester1]] (irc_nick3), [[User:Tester2|Tester2]] (irc_nick4), [[User:Tester3|Tester3]] (irc_nick5)
 
  
== Prerequisite for Test Day ==
+
Learn more about [[Test_Day:2011-04-28_Cloud_SIG_BoxGrinder_Build|BoxGrinder Test Day]].
  
List any prerequisite needs for the test event.  A fresh system, virtualized guest, a blank DVD ... a desire to break software?
+
== Fedora on EC2 ==
  
* Usb key
+
Learn more about [[Test_Day:2011-04-28_Cloud_SIG_Fedora_EC2|Fedora on EC2]].
* 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. Replace XX with whatever Fedora release is pending:
+
  [[Category:Fedora 15 Test Days]]
 
 
* An updated [http://fedoraproject.org/get-prerelease Fedora XX 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):
 
 
 
* 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 (again, replace XX as above):
 
 
 
=== '''Update your machine''' ===
 
 
 
If you're running Fedora XX, 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 Rawhide 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]].
 
 
 
== 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 some instructions on how to report bugs, and any special instructions. Here's an example, from a Palimpsest test day:
 
 
 
If you have problems with any of the tests, report a bug to [https://bugzilla.redhat.com Bugzilla] usually for the component [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=13&component=udisks udisks], or [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=13&component=gnome-disk-utility gnome-disk-utility] for bugs in the Palimpsest graphical front end itself. If you are unsure about exactly how to file the report or what other information to include, just ask on IRC and we will help you. Once you have completed the tests, add your results to the Results table below, following the example results from the first line as a template. The first column should be your name with a link to your User page in the Wiki if you have one, and the second should be a link to the Smolt profile of the system you tested. For each test case, use the [[Template:result|result template]] to enter your result, as shown in the example result line.
 
 
 
{|
 
! User
 
! Smolt Profile
 
! [[QA:Testcase_sample_1|Sample test 1]]
 
! [[QA:Testcase_sample_2|Sample test 2]]
 
! [[QA:Testcase_sample_3|Sample test 3]]
 
! [[QA:Testcase_sample_4|Sample test 4]]
 
! References
 
|-
 
| [[User:SampleUser|Sample User]]
 
| [http://www.smolts.org/client/show/pub_84465125-1350-4f83-87b9-5f16f7430eb8 HW]
 
| {{result|none}}
 
| {{result|pass}}
 
| {{result|warn}} <ref>Test pass, but also encountered {{bz|54321}}</ref>
 
| {{result|fail}} <ref>{{bz|12345}}</ref>
 
| <references/>
 
|-
 
|}
 
 
 
[[Category:Fedora 15 Test Days]]
 

Latest revision as of 21:20, 26 June 2015

Cloud SIG Fedora Test Day
Echo-testing-48px.png
Fedora on EC2, BoxGrinder

Date 2011-04-28
Time all day

Website QA/Fedora_15_test_days
IRC #fedora-test-day (webirc)
Mailing list cloud


Note.png
Can't make the date?
If you come to this page before or after the test day is completed, your testing is still valuable, and you can use the information on this page to test, file any bugs you find at Bugzilla, and add your results to the results section. If this page is more than a month old when you arrive here, please check the current schedule and see if a similar but more recent Test Day is planned or has already happened.

What to test?[edit]

Today's instalment of Fedora Test Day will focus on BoxGrinder Build and Fedora on EC2.

Detailed information about tests for selected feature is available on features page listed below.

BoxGrinder Build[edit]

Learn more about BoxGrinder Test Day.

Fedora on EC2[edit]

Learn more about Fedora on EC2.