fltg May 2013

fltg@lists.stg.fedoraproject.org

3 participants
4 discussions

[Fedora QA] #344: Fedora 19 i18n Test Day
by fedora-badges 06 Jun '13

06 Jun '13

#344: Fedora 19 i18n Test Day ----------------------+------------------------ Reporter: aalam | Owner: Type: task | Status: new Priority: major | Milestone: Fedora 19 Component: Test Day | Version: Keywords: | Blocked By: Blocking: | ----------------------+------------------------ we need to have Fedora 19 i18n Test Day. Date can be decided during i18n Team meeting tomorrow, for which ticket created. https://fedorahosted.org/i18n/ticket/17 -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/344> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 10

[Fedora QA] #345: Fedora 19 Translation (l10n) Test Day
by fedora-badges 06 Jun '13

06 Jun '13

#345: Fedora 19 Translation (l10n) Test Day ----------------------+------------------------ Reporter: aalam | Owner: Type: task | Status: new Priority: major | Milestone: Fedora 19 Component: Test Day | Version: Keywords: | Blocked By: Blocking: | ----------------------+------------------------ (From Fedora 18), Filing separate Ticket for Fedora Translation day selection. Either date can be before (2013-04-02) Software String Freeze - March 28 or before - (2013-05-07) Beta Change Deadline - May 02 May 02 can be more preferable with more stable build to test + major translations available to test with almost all feature available Fedora 18 Ticket for Reference: https://fedorahosted.org/fedora-qa/ticket/301#no3 -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/345> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 7

Feedback on i18n test cases
by Ani Peter 01 May '13

01 May '13

Few suggestions are listed down, which were found during the dry run of the i18n test cases: 1. Each time after you do the testing, need to to come back to the test day page and then scroll down to go the Result section Suggestion: Provide the link for result page on each test case page and also link each result page to the test case page. ie. In the "Input (Overall) section, we have two test cases: QA:Testcase i18n ibus input and QA:Gnome Input Method Integration IBus. (i) Provide the link for the result page of Input (Overall) in these two test cases' page so that from tester perspective navigating between test case and result pages will be easier. (ii) Also can provide these two test cases' pages link in the Input(Overall) result page 2. QA:Testcase ibus input: Found the instructions bit confusing and difficult to understand 3. Input (language-specific): Didnt find the command to run the typing booster application. Thanks Ani

3 6

Tracker bug for F19 L10N QA Test
by Noriko Mizumoto 01 May '13

01 May '13

Hi, I've labelled the bugs filed with 'F19L10nTestday' in whiteboard field for tracking purpose, and also created the tracker bug #958376. Now I can see that there are 22 bugs filed, while 2 bugs have been resolved so far. noriko

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

fltg May 2013