From Fedora Project Wiki
(Make some modification to this page)
Line 5: Line 5:
| DATE || TIME || WHERE
| DATE || TIME || WHERE
|-
|-
| '''2010-09-09''' || 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-09-09''' || All Day || [irc://irc.freenode.net/fedora-test-day #fedora-test-day] ([http://webchat.freenode.net/?channels=fedora-test-day webirc])
|-
|-
|}
|}
Line 13: Line 13:
== What to test? ==
== What to test? ==


Today's installment of Fedora Test Day will focus on translations and keyboard layout support in Anaconda
Today's installment of Fedora Test Day will focus on '''translations and keyboard layout support in Anaconda'''


== Who's available ==
== Who's available ==
Line 22: Line 22:


== 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?


* One or more keyboards with different layouts.
* One or more keyboards with different layouts.
* An updated [http://fedoraproject.org/get-prerelease Fedora 14 pre-release] or a [http://alt.fedoraproject.org/pub/alt/nightly-composes/desktop/ nightly live image]
* Bare metal or virtual machine.
* Your hardware profile uploaded to [http://www.smolts.org Smolt] according to [http://smolts.org/smolt-wiki/Main_Page#Usage these instructions]
* Usb key, a virtualized guest or a burned CD with the test image
* Usb key, a virtualized guest or a liveCD with the test image


== How to test? ==
== How to test? ==


=== '''Live image''' ===
== Prepare Your System ==


Optionally, you may download a non-destructive Fedora 14 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].
* Tests requiring ''physical media'' (e.g. DVD or CD images) -- [http://serverbeach1.fedoraproject.org/pub/alt/stage download the required ISO images].
* Unless otherwise noted, you may use nightly Fedora 14 ''branch'' install images.  [[Releases/Branched|Review for information on downloading and installing Branched]].
* Optionally, you may download a non-destructive Fedora 14 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 ==
== Test Cases ==
Line 50: Line 49:


== 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 some instructions on how to report bugs, and any special instructions. Here's an example, from a Palimpsest test day:


Specific L10N bugs like typos and translation mistakes should be directly reported to the local translation team mailing list or a bug report should be filed at [https://bugzilla.redhat.com/ Bugzilla] against the related language. General bugs that affect all languages like strings not marked for translation, downstream patching that breaks translations and input method issues should be filed against the related package. 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.
Specific L10N bugs like typos and translation mistakes should be directly reported to the local translation team mailing list or a bug report should be filed at [https://bugzilla.redhat.com/ Bugzilla] against the related language. General bugs that affect all languages like strings not marked for translation, downstream patching that breaks translations and input method issues should be filed against the related package. 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.
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 '''<nowiki>{{result|pass}}</nowiki>'''. If you had trouble, enter the word '''<nowiki>{{result|warn}}<ref>xxx</ref></nowiki>''' or '''<nowiki>{{result|fail|bug No}}</nowiki>''', 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.


{|
{| class="wikitable sortable" border="1"
! User
! User
! Smolt Profile
! Test Description
! [[QA:Testcase_sample_1|Sample test 1]]
! Result
! [[QA:Testcase_sample_2|Sample test 2]]
! [[QA:Testcase_sample_3|Sample test 3]]
! [[QA:Testcase_sample_4|Sample test 4]]
! References
! References
|-
|-
| [[User:SampleUser|Sample User]]
| [[User:SampleUser|Sample User]]
| [http://www.smolts.org/client/show/pub_84465125-1350-4f83-87b9-5f16f7430eb8 HW]
| Asian Language Install - Chinese
| {{result|none}}
| {{result|pass}}
| {{result|pass}}
| {{result|warn}} <ref>Test pass, but also encountered {{bz|54321}}</ref>
{{result|warn}} <ref>Test pass, but also encountered {{bz|54321}}</ref>
| {{result|fail}} <ref>{{bz|12345}}</ref>
{{result|fail}} <ref>{{bz|12345}}</ref>
| <references/>
| <references/>
|-
|-
|
|
| {{result|none}}
|
|}
|}


[[Category:Test Days]]
[[Category:Fedora 14 Test Days]]

Revision as of 06:35, 18 August 2010

Warning.png
This page is a draft only
It is still under construction and content may change. Do not rely on the information on this page.
DATE TIME WHERE
2010-09-09 All Day #fedora-test-day (webirc)
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 - 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 translations and keyboard layout support in Anaconda

Who's available

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

Prerequisite for Test Day

  • One or more keyboards with different layouts.
  • Bare metal or virtual machine.
  • Usb key, a virtualized guest or a burned CD with the test image

How to test?

Prepare Your System

Test Cases

Translation test results template:

i18n installation test cases:


Test Results

Specific L10N bugs like typos and translation mistakes should be directly reported to the local translation team mailing list or a bug report should be filed at Bugzilla against the related language. General bugs that affect all languages like strings not marked for translation, downstream patching that breaks translations and input method issues should be filed against the related package. 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 {{result|pass}}. If you had trouble, enter the word {{result|warn}}<ref>xxx</ref> or {{result|fail|bug No}}, 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.

User Test Description Result References
Sample User Asian Language Install - Chinese
Pass pass
Warning warn
[1]
Fail fail
[2]
  1. ↑ Test pass, but also encountered RHBZ #54321
  2. ↑ RHBZ #12345
none
Retrieved from "https://fedoraproject.org/w/index.php?title=Test_Day:2010-09-16_AnacondaTranslationKeyboard&oldid=193101"