From Fedora Project Wiki

(here's a test day, whee)
Line 3: Line 3:
 
| image = [[File:Echo-testing-48px.png|link=QA/Fedora_22_test_days]]
 
| image = [[File:Echo-testing-48px.png|link=QA/Fedora_22_test_days]]
 
| caption = Software Center and Apper
 
| caption = Software Center and Apper
| date = 2015-04-23
+
| date = 2015-04-30
 
| time = all day
 
| time = all day
 
| website = [[QA/Fedora_22_test_days]]
 
| website = [[QA/Fedora_22_test_days]]
Line 19: Line 19:
  
 
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)
+
* Quality Assurance - [[User:Adamwill|Adam Williamson]] (adamw), [[User:Roshi|Mike Ruckman]] (roshi)
* 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?
+
* A [http://fedoraproject.org/get-prerelease Fedora 22 Beta] (or Final TC1) installation: Workstation to test Software Center, KDE to test Apper
 
 
* 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 [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]
 
  
 
== How to test? ==
 
== How to test? ==
  
High level details on how a contributor can get involved. This can include (but not limited to):
+
Install the Fedora 22 Beta image, and then perform one or more of the test cases from the list below. Enter your results into the [[#Test Results|results table]], following the instructions above it.
  
* Areas to target with exploratory testing
+
== Test Cases ==
* A list of pre-defined test cases to execute
 
* How to report back results
 
  
Here's another common chunk (again, replace XX as above):
+
[[QA:Testcase_package_install_remove]]
 +
[[QA:Testcase_desktop_update_graphical]]
 +
[[QA:Testcase_desktop_update_notification]]
  
=== '''Update your machine''' ===
+
== Test Results ==
  
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:
+
If you have problems with any of the tests, report a bug to [https://bugzilla.redhat.com Bugzilla]:
  
=== '''Live image''' ===
+
* [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=22&component=gnome-software gnome-software]
 +
* [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=22&component=apper apper]
  
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].
+
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 appropriate table below (there is one for GNOME Software and one for Apper), 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. For each test case, use the [[Template:result|result template]] to enter your result, as shown in the example result line.
  
== Test Cases ==
+
=== GNOME Software ===
  
Provide a list of test areas or test cases that you'd like contributors to execute.  For other examples, see [[:Category:Test_Cases]].
+
{|
 
+
! User
== Test Results ==
+
! [[QA:Testcase_package_install_remove|Install / remove]]
 
+
! [[QA:Testcase_desktop_update_graphical|Update]]
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:
+
! [[QA:Testcase_desktop_update_notification|Update notification]]
 +
! References
 +
|-
 +
| [[User:SampleUser|Sample User]]
 +
| {{result|none}}
 +
| {{result|pass}}
 +
| {{result|fail|12345}}
 +
| <references/>
 +
|-
 +
|}
  
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. For each test case, use the [[Template:result|result template]] to enter your result, as shown in the example result line.
+
=== Apper ===
  
 
{|
 
{|
 
! User
 
! User
! [[QA:Testcase_sample_1|Sample test 1]]
+
! [[QA:Testcase_package_install_remove|Install / remove]]
! [[QA:Testcase_sample_2|Sample test 2]]
+
! [[QA:Testcase_desktop_update_graphical|Update]]
! [[QA:Testcase_sample_3|Sample test 3]]
+
! [[QA:Testcase_desktop_update_notification|Update notification]]
! [[QA:Testcase_sample_4|Sample test 4]]
 
 
! References
 
! References
 
|-
 
|-
Line 74: Line 73:
 
| {{result|none}}  
 
| {{result|none}}  
 
| {{result|pass}}
 
| {{result|pass}}
| {{result|warn}} <ref>Test pass, but also encountered {{bz|54321}}</ref>
+
| {{result|fail|54321}}
| {{result|fail}} <ref>{{bz|12345}}</ref>
 
 
| <references/>
 
| <references/>
 
|-
 
|-

Revision as of 01:25, 30 April 2015

Fedora Test Days
Echo-testing-48px.png
Software Center and Apper

Date 2015-04-30
Time all day

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


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?

Today's instalment of Fedora Test Day will focus on Software Center and Apper

Who's available

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

Prerequisite for Test Day

  • A Fedora 22 Beta (or Final TC1) installation: Workstation to test Software Center, KDE to test Apper

How to test?

Install the Fedora 22 Beta image, and then perform one or more of the test cases from the list below. Enter your results into the results table, following the instructions above it.

Test Cases

QA:Testcase_package_install_remove QA:Testcase_desktop_update_graphical QA:Testcase_desktop_update_notification

Test Results

If you have problems with any of the tests, report a bug to Bugzilla:

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 appropriate table below (there is one for GNOME Software and one for Apper), 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. For each test case, use the result template to enter your result, as shown in the example result line.

GNOME Software

User Install / remove Update Update notification References
Sample User
none
Pass pass
Fail fail 12345

Apper

User Install / remove Update Update notification References
Sample User
none
Pass pass
Fail fail 54321