Test Day:2015-04-21 FedUp: Difference between revisions

Revision as of 04:44, 21 April 2015

Fedora Test Days

FedUp

Date	2015-04-21
Time	all day

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

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 FedUp

Who's available

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

Development - Will Woods (wwoods)
Quality Assurance - Adam Williamson (adamw), Petr Schindl (pschindl)

Prerequisite for Test Day

A system with Fedora 20 or 21 you can use for test purposes (i.e. you don't mind if it all goes wrong and you lose the system)! Testing with a virtual machine will be useful for many cases, and will let you run multiple tests easily.

How to test?

The test procedure is simply to take a Fedora 20 or Fedora 21 installation and upgrade it to Fedora 22. To ensure you get the latest fedup for testing, run yum --enablerepo=updates-testing install fedup or yum --enablerepo=updates-testing update fedup first. To upgrade, run fedup --network 22 --instrepo https://dl.fedoraproject.org/pub/alt/stage/22_Beta_RC3/Server/(arch)/os, where (arch) is the appropriate architecture (armhfp, x86_64, or i386).

The idea is to test upgrades from as many different starting situations as possible - particularly with different package sets, languages, keyboard layouts, and storage configurations.

If the upgrade completes successfully, test the upgraded system to ensure it works correctly.

Test Results

If any of your upgrades fails (or leads to a broken system), report a bug to Bugzilla. The correct component will depend on the exact nature of the bug - ask in IRC if you're unsure. If you can't find out what component to file against, file the bug against usually for the component fedup. Include any useful details about the system's configuration, and note that your result is part of this Test Day and mention that you followed the instructions on this page.

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. In the 'Results' column, you can link to bug reports of any failed tests, and very briefly summarize your results. Please don't post long comments here, it will make the table hard to read: anything longer than a few words is likely fodder for a bug report, or mailing list post, or you can use <ref>comment</ref> to make the comment appear as a footnote below the table.

User	Results
Sample User	2 pass 2 fail, RHBZ #12345 RHBZ #54321

@@ Line 19: / Line 19: @@
 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:Wwoods|Will Woods]] (wwoods)
-* Quality Assurance - [[User:Tester1|Tester1]] (irc_nick3), [[User:Tester2|Tester2]] (irc_nick4), [[User:Tester3|Tester3]] (irc_nick5)
+* Quality Assurance - [[User:Adamwill|Adam Williamson]] (adamw), [[User:Pschindl|Petr Schindl]] (pschindl)
 == 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 system with Fedora 20 or 21 you can use for test purposes (i.e. you don't mind if it all goes wrong and you lose the system)! Testing with a virtual machine will be useful for many cases, and will let you run multiple tests easily.
-* 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? ==
-High level details on how a contributor can get involved.  This can include (but not limited to):
+The test procedure is simply to take a Fedora 20 or Fedora 21 installation and upgrade it to Fedora 22. To ensure you get the latest fedup for testing, run {{command|<nowiki>yum --enablerepo=updates-testing install fedup</nowiki>}} or {{command|<nowiki>yum --enablerepo=updates-testing update fedup</nowiki>}} first. To upgrade, run {{command|<nowiki>fedup --network 22 --instrepo https://dl.fedoraproject.org/pub/alt/stage/22_Beta_RC3/Server/(arch)/os</nowiki>}}, where (arch) is the appropriate architecture (armhfp, x86_64, or i386).
-* 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 ==
+The idea is to test upgrades from as many different starting situations as possible - particularly with different package sets, languages, keyboard layouts, and storage configurations.
-Provide a list of test areas or test cases that you'd like contributors to execute.  For other examples, see [[:Category:Test_Cases]].
+If the upgrade completes successfully, test the upgraded system to ensure it works correctly.
 == 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 any of your upgrades fails (or leads to a broken system), report a bug to [https://bugzilla.redhat.com Bugzilla]. The correct component will depend on the exact nature of the bug - ask in IRC if you're unsure. If you can't find out what component to file against, file the bug against usually for the component [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=22&component=fedup fedup]. Include any useful details about the system's configuration, and note that your result is part of this Test Day and mention that you followed the instructions on this page.
-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.
+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. In the 'Results' column, you can link to bug reports of any failed tests, and '''very briefly''' summarize your results. Please don't post long comments here, it will make the table hard to read: anything longer than a few words is likely fodder for a bug report, or mailing list post, or you can use {{code|<nowiki><ref>comment</ref></nowiki>}} to make the comment appear as a footnote below the table.
 {|
 ! User
-! [[QA:Testcase_sample_1|Sample test 1]]
+! Results
-! [[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]]
-| {{result|none}}
+| 2 pass 2 fail, {{bz|12345}} {{bz|54321}}
-| {{result|pass}}
-| {{result|warn}} <ref>Test pass, but also encountered {{bz|54321}}</ref>
-| {{result|fail}} <ref>{{bz|12345}}</ref>
-| <references/>
 |-
 |}
+<references/>
 [[Category:Fedora 22 Test Days]]

Search