test January 2015

test@lists.fedoraproject.org

63 participants
188 discussions

[Fedora QA] #404: Look through validation matrices and note which tests don't apply to ARM
by fedora-badges 30 Jan '15

30 Jan '15

#404: Look through validation matrices and note which tests don't apply to ARM ----------------------+------------------------ Reporter: adamwill | Owner: pwhalen Type: task | Status: new Priority: blocker | Milestone: Fedora 20 Component: Wiki | Version: Keywords: | Blocked By: Blocking: | ----------------------+------------------------ In the effort to revise the validation pages for ARM, it would help a lot to know which test cases in the existing set are not sensibly applicable to ARM validation. If an ARM folk could go through the pages and list which cases do not apply, that'd be great. Please refer to: * https://fedoraproject.org/wiki/QA:Fedora_20_Install_Results_Template * https://fedoraproject.org/wiki/QA:Base_validation_results_template * https://fedoraproject.org/wiki/QA:Desktop_validation_results_template Thanks! -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/404> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 5

[Fedora QA] #403: Modify initial-setup test case or create new one for ARM (vendor mode)
by fedora-badges 30 Jan '15

30 Jan '15

#403: Modify initial-setup test case or create new one for ARM (vendor mode) ------------------------+------------------------ Reporter: adamwill | Owner: pwhalen Type: task | Status: new Priority: blocker | Milestone: Fedora 20 Component: Test cases | Version: Keywords: arm | Blocked By: Blocking: | ------------------------+------------------------ The initial-setup test case - https://fedoraproject.org/wiki/QA:Testcase_base_initial_setup - doesn't really cover the case where initial-setup runs in 'vendor mode'. This mode is currently used only for ARM pre-built images, but since ARM is now primary arch, we need a test case for it. It should be basically a more extensive version of the test case that covers all the bits that would be release blocking for ARM (which I think is language, root password, user password, date/time - really all of it). If the existing test case can be 'conditionalized' elegantly enough, that'd be okay, otherwise just create a variant of it. -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/403> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 3

[Fedora QA] #397: Create test cases for release criteria that are currently missing them
by fedora-badges 30 Jan '15

30 Jan '15

1 5

[Fedora QA] #400: Revise 'firstboot' test case
by fedora-badges 30 Jan '15

30 Jan '15

#400: Revise 'firstboot' test case ------------------------+------------------------ Reporter: adamwill | Owner: adamwill Type: defect | Status: new Priority: major | Milestone: Fedora 20 Component: Test cases | Version: Keywords: | Blocked By: Blocking: | ------------------------+------------------------ We've fixed up the release criteria for the F19 changes to replace firstboot with initial-setup and gnome-initial-setup and allow user creation in anaconda, but we still have the firstboot test case: https://fedoraproject.org/wiki/QA:Testcase_base_firstboot And the startup test case: https://fedoraproject.org/wiki/QA:Testcase_base_startup assumes the firstboot path too. We should revise those for the new era and the new criterion. -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/400> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 2

[Fedora QA] #396: Revise partitioning test cases to reflect newUI design and cover its intended use cases
by fedora-badges 30 Jan '15

30 Jan '15

#396: Revise partitioning test cases to reflect newUI design and cover its intended use cases ----------------------+------------------------ Reporter: adamwill | Owner: Type: task | Status: new Priority: major | Milestone: Fedora 20 Component: Wiki | Version: Keywords: | Blocked By: Blocking: | ----------------------+------------------------ Our current set of 'partitioning test cases' is: * https://fedoraproject.org/wiki/QA:Testcase_Anaconda_autopart_install * https://fedoraproject.org/wiki/QA:Testcase_Anaconda_autopart_(use_free_spac… * https://fedoraproject.org/wiki/QA:Testcase_Anaconda_autopart_(reclaim)_inst… * https://fedoraproject.org/wiki/QA:Testcase_Anaconda_autopart_(encrypted)_in… * https://fedoraproject.org/wiki/QA:Testcase_anaconda_ext4_rootfs_on_disk_par… * https://fedoraproject.org/wiki/QA:Testcase_Anaconda_custom_partitioning * https://fedoraproject.org/wiki/QA:Testcase_Partitioning_On_Software_RAID * https://fedoraproject.org/wiki/QA:Testcase_dualboot_with_windows * https://fedoraproject.org/wiki/QA:Testcase_anaconda_btrfs_rootfs_on_disk_pa… * https://fedoraproject.org/wiki/QA:Testcase_anaconda_ext3_rootfs_on_disk_par… * https://fedoraproject.org/wiki/QA:Testcase_anaconda_xfs_rootfs_on_disk_part… * https://fedoraproject.org/wiki/QA:Testcase_Partitioning_No_Swap * https://fedoraproject.org/wiki/QA:Testcase_Anaconda_autopart_(shrink)_insta… This is kind of a mish-mash of functional and exploratory testing, covering some areas but leaving other large areas entirely uncovered. Several of the tests are also clearly based on the design of the *old* installer's partitioning workflow. At minimum we need to go through the existing cases and ensure the text is correct for the newUI partitioning design. Really, what we need to do is step back and take a wider look at the functionality that is most essential to the newUI design, with reference to the revised release criteria, and revise the entire set of partitioning test cases to cover the most important workflows, including ones we are missing like 're-use existing partitions', 'LVM-on-RAID', the intricacies of UEFI vs. BIOS and ms-dos vs. gpt partitioning, and probably some others I'm forgetting. This may need to be a 'master ticket' and have several smaller sub- tickets, depending on how much work we decide to do on it. -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/396> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 4

[Fedora QA] #394: Revise validation process / templates for ARM as primary arch
by fedora-badges 30 Jan '15

30 Jan '15

#394: Revise validation process / templates for ARM as primary arch ----------------------+------------------------ Reporter: adamwill | Owner: Type: task | Status: new Priority: major | Milestone: Fedora 20 Component: Wiki | Version: Keywords: | Blocked By: Blocking: | ----------------------+------------------------ ARM has been accepted as a primary arch at least for buildsystem purposes. The plan is to have 'primary' ARM deliverables as well if possible. This may require us to revise the validation process / template pages to incorporate ARM testing. It may be as 'simple' as throwing a couple of extra columns (for the two ARM variants) alongside x86_64, i686 and EFI in the templates, but we will have to take a look. -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/394> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 6

[Fedora QA] #393: Revise release criteria for ARM as primary arch
by fedora-badges 30 Jan '15

30 Jan '15

#393: Revise release criteria for ARM as primary arch ------------------------------+------------------------ Reporter: adamwill | Owner: adamwill Type: task | Status: new Priority: major | Milestone: Fedora 20 Component: Release criteria | Version: Keywords: | Blocked By: Blocking: | ------------------------------+------------------------ ARM has been accepted as a primary arch at least for buildsystem purposes. The plan is to have 'primary' ARM deliverables as well if possible. This may require adjustments to the release criteria: we should co-ordinate this with the owners of the owners of https://fedoraproject.org/wiki/Changes/ARM_as_Primary (dgilmore and pbrobinson). -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/393> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 14

[Fedora QA] #363: Require spins to go through smoke testing before being published
by fedora-badges 30 Jan '15

30 Jan '15

#363: Require spins to go through smoke testing before being published -------------------------+---------------------------------- Reporter: adamwill | Owner: Type: enhancement | Status: new Priority: minor | Milestone: Undetermined Future Component: Test cases | Version: Keywords: | Blocked By: Blocking: | -------------------------+---------------------------------- = problem = Sometimes, we publish spins that are completely DOA. = analysis = There is no mandatory testing of any Fedora images beyond netinst, DVD and the two release blocking desktop live spins, as things stand, but we publish rather more spins than that. In practice we test Xfce, LXDE, SoaS and AMI images to some extent, but others are rarely touched. = enhancement recommendation = viking-ice has suggested that we should produce some kind of validation matrix which has very basic, generic smoke tests: basically, does the image at least boot up sanely? We would require there to be a PASS for these mandatory smoke tests present in that matrix for a spin image to be published on the spins page. QA does not commit to doing the actual testing; we may do so if we have time, but ultimately, if a spin owner wants to have their spin published, it's their responsibility to get the testing done, either by poking QA, doing it themselves, or getting someone else to do it. -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/363> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 1

[Fedora QA] #336: ARM as primary arch
by fedora-badges 30 Jan '15

30 Jan '15

#336: ARM as primary arch ------------------------------+------------------------ Reporter: jdulaney | Owner: Type: task | Status: new Priority: major | Milestone: Fedora 19 Component: Release criteria | Version: Keywords: | Blocked By: Blocking: | ------------------------------+------------------------ I'm opening this ticket to track integrating ARM into the current QA process. Paul Whalen is my contact from the ARM side; at FUDCon I gave him the 30,000' view of the current QA process. -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/336> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 6

[Fedora QA] #327: test cases that require autopart shrink need to be updated
by fedora-badges 30 Jan '15

30 Jan '15

#327: test cases that require autopart shrink need to be updated ------------------------+------------------------ Reporter: kparal | Owner: Type: defect | Status: new Priority: major | Milestone: Fedora 18 Component: Test cases | Version: Keywords: | Blocked By: Blocking: | ------------------------+------------------------ Anaconda removed shrink option from guided part, now you need to do custom part to achieve it. The test cases must be adjusted to reflect that. See https://bugzilla.redhat.com/show_bug.cgi?id=891881 * https://fedoraproject.org/wiki/QA:Testcase_Anaconda_autopart_%28shrink%29_i… * https://fedoraproject.org/wiki/QA:Testcase_dualboot_with_windows -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/327> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 6

← Newer
1
2
3
4
5
6
7
8
...
19
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

test January 2015