Test Day:2010-08-26 OpenSCAP: Difference between revisions

Revision as of 09:05, 17 August 2010

DATE	TIME	WHERE
2010-08-26	From 9:00 to 17:00 UTC	#fedora-test-day (webirc)

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 - which should be linked at QA/Test_Days - and see if a similar but more recent Test Day is planned or has already happened.

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:

Development - Peter Vrabec (wrabco), <<FIXME>>
Quality Assurance - Kamil Páral (kparal)

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. Replace XX with whatever Fedora release is pending:

An updated Fedora XX pre-release, Rawhide (tips on installing Rawhide below), or a nightly live image
Your hardware profile uploaded to Smolt according to 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 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 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

If you have problems with any of the tests, report a bug to Bugzilla for the openscap component. 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.

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

[1] Test pass, but also encountered RHBZ #54321

[2] RHBZ #12345

[1]

[2]

@@ Line 3: / Line 3: @@
 | DATE || TIME || WHERE
 |-
-| '''<<FIXME>>''' || 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])
+| 2010-08-26 || From ''9:00'' to ''17:00'' UTC || [irc://irc.freenode.net/fedora-test-day #fedora-test-day] ([http://webchat.freenode.net/?channels=fedora-test-day webirc])
 |-
 |}
@@ Line 15: / Line 15: @@
 == 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:
-* Development - [[User:Developer1|Developer1]] (irc_nick1), [[User:Developer2|Developer2]] (irc_nick2)
+* Development - [[User:pvrabec|Peter Vrabec]] (wrabco), '''<<FIXME>>'''
-* Quality Assurance - [[User:Tester1|Tester1]] (irc_nick3), [[User:Tester2|Tester2]] (irc_nick4), [[User:Tester3|Tester3]] (irc_nick5)
+* Quality Assurance - [[User:kparal|Kamil Páral]] (kparal)
 == Prerequisite for Test Day ==
@@ Line 57: / Line 57: @@
 == 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 Bugzilla for the [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=13&component=openscap openscap component]. 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.
-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, if your system worked correctly, simply enter the word '''PASS'''. If you had trouble, enter the word '''FAIL''', with a footnote indicator, and put a link to the bug report in the References column (as in the example line). For tests you could not perform, enter a dash.
 {|

Search