Re: Testing impact of Red Hat office closure
> On Mon, 2020-03-16 at 18:52 +0100, Kamil Paral wrote: > > On Sun, Mar 15, 2020 at 3:49 PM Ben Cotton wrote: > > > > > Hi QA team, > > > > > > As many of you may already know, Red Hat has asked all employees to work > > > from home[1]. Given the current global conditions, I want to start > > > understanding the impact if Red Hat offices are closed as we approach the > > > Fedora 32 Final (currently targeted for 21 April). > > > > > > What tests require physical hardware that resides in Brno or other > > > offices? > > > > > > > Hi, regarding just the Brno office (i.e. skipping tests that we couldn't do > > anyway), and looking at our matrices [1]: > > > > * Testcase_Boot_default_install (i.e. the whole "Default boot and install" > > section) -- This is going to apply to everything that *requires* a bare > > metal machines, like this test case. Folks often don't have spare bare > > metal machines that they can fully reinstall several times per day. And > > when they do, it might be something slow, or it might not be able to boot > > in UEFI mode (as is my case, an old notebook which takes an hour to install > > and 5 minutes to boot, BIOS only). So our performance in these cases is > > likely to be severely affected. This might prevent any "test this RC in 24 > > hours" efforts (that is also related to a narrow bandwidth Internet for > > some of us). > > I have a dedicated test box that can do an install in twenty minutes or > so and works fine for both BIOS and UEFI installs. So I can cover a lot > of these tests if necessary. I might need a faster USB stick though... > > > * Testcase_install_to_firmware_RAID -- Firmware RAID is in one of our > > office test machines, we probably can't evaluate this one. > > My test box has firmware RAID, but it's a controller the kernel doesn't > support :/ This is one we need to find someone to cover. > > > * Testcase_Anaconda_User_Interface_Basic_Video_Driver -- This will likely > > be affected by a more limited selection of bare metals we'll have access to > > (often older to what is in our office, which is old already). > > My test box has a Radeon adapter, IIRC, and I can run this test on it. > I can also boot a live image (although not really run an install) to > basic mode on my laptops, which have Intel and NVIDIA. > > > * Testcase_dualboot_with_windows -- This will be affected by the lack of > > bare metal machines. > > * Testcase_dualboot_with_macOS -- Our old Mac Mini stayed in the office, so > > we can't evaluate this one. OTOH, our tests decrease in value every cycle, > > because our Mac is archaic and doesn't even contain the latest OS version, > > so it differs very much from what is commonly available on the market these > > days. > > In future we should probably request some budget to get a newer Mac. I > can't really help with either of these easily (don't have a test box > with Windows on any more), unfortunately. > > > * Testcase_audio_basic, Testcase_desktop_menus, Testcase_desktop_automount > > -- These might be harder to check with the exact RC due to limited access > > to bare metal (unless we want to reinstall our own laptops each time). This > > mostly affects certain applications that often behave differently on bare > > metal than in a VM, like video players, or testing hw-only stuff like USB, > > webcam, suspend, etc. But since we all run F32 now (I think), our own > > laptops provide us with a decent level of certainty that that stuff works > > (even when we're not in that exact software configuration). > > * Testcase_Printing_New_Printer (real printer) - Only few people have a > > real printer at home, I think. I don't. > > I have one, though it's usually connected by ethernet, I can probably > temporarily connect it via USB to my test box to check this. > > > Regarding our Beijing office, I think these will be affected as well: > > * Testcase_install_to_FCoE_target > > * Testcase_install_to_multipath > > I *think* Lili actually accesses these via Beaker, so they still may be > possible. yeah, basically not affected. Best Regards, Lili > -- > Adam Williamson > Fedora QA Community Monkey > IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net > http://www.happyassassin.net > ___ > test mailing list -- test@lists.fedoraproject.org > To unsubscribe send an email to test-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org > ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines:
Re: update some test cases
From: Adam Williamson adamw...@fedoraproject.org To: For testing and quality assurance of Fedora releases test@lists.fedoraproject.org Sent: Wednesday, January 21, 2015 6:50:04 AM Subject: Re: update some test cases On Wed, 2015-01-14 at 23:59 -0500, Lili Nie wrote: Hi Adam, Thanks a lot for your great advice and help :) No problem! I see you put the changes into place, I just went through the tests and cleaned up a bit more - I created the new template I suggested for the steps all the test cases shared, and tweaked the wording a bit in other places. yeah,I thought I had received pretty much advice:) Thanks again! you have grabbed my words,haha,Thanks a lot again. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: update some test cases
- Original Message -
From: Adam Williamson adamw...@fedoraproject.org
To: For testing and quality assurance of Fedora releases
test@lists.fedoraproject.org
Sent: Thursday, January 15, 2015 2:48:28 AM
Subject: Re: update some test cases
On Tue, 2015-01-13 at 03:01 -0500, Lili Nie wrote:
Hi all,
I'm intending to modify some test cases in the Fedora test wiki
pages,as shown in the following:
https://fedoraproject.org/wiki/QA:Testcase_Partitioning_No_Swap
How to test
Boot the installer using any available means (netinst/boot.iso,
PXE, or DVD)
on INSTALLATION SUMMARY screen, click into Installation
Destination
select I will configure partitioning on the Installation
Destination page,and proceed with installation
On the Manual Partitioning screen, ensure no swap partition is
created
Complete the installation
https://fedoraproject.org/wiki/QA:Testcase_anaconda_ext3_rootfs_on_disk_partition
How to test
Boot the installer using any available means (netinst/boot.iso,
PXE, or DVD)
on INSTALLATION SUMMARY screen, click into Installation
Destination
select I will configure partitioning on the Installation
Destination page,and proceed with installation
On the Manual Partitioning screen, place the root filesystem(/)
on an ext3 formatted partition
Complete the installation
https://fedoraproject.org/wiki/QA:Testcase_anaconda_xfs_rootfs_on_disk_partition
How to test
Boot the installer using any available means (netinst/boot.iso,
PXE, or DVD)
on INSTALLATION SUMMARY screen, click into Installation
Destination
select I will configure partitioning on the Installation
Destination page,and proceed with installation
On the Manual Partitioning screen, place the root filesystem(/)
on an xfs formatted partition
Complete the installation
https://fedoraproject.org/wiki/QA:Testcase_anaconda_btrfs_rootfs_on_disk_partition
How to test
Boot the installer using any available means (netinst/boot.iso,
PXE, or DVD)
On INSTALLATION SUMMARY screen, click into Installation
Destination
select I will configure partitioning on the Installation
Destination page,and proceed with installation
On the Manual Partitioning screen, place the root filesystem(/)
on a btrfs formatted partition
Complete the installation
Hi Lili!
My suggestion is to use mediawiki's template system to avoid
duplicating the same steps in multiple test cases. I actually already
did this for some of the partitioning test cases, but not all. You can
look at the test cases in the Guided storage configuration section
for ideas.
There are already four templates you can use:
{{Template:Partitioning_single_setup}} (for the setup section)
{{Template:Partitioning_actions}} (for the first few actions steps)
{{Template:Partitioning_actions_post}} (for after all test-case
specific steps, it just says 'complete the install making sensible
choices for everything else')
{{Template:Partitioning_results}} (for the results - it's a generic
text which should apply to all/most partitioning test cases)
It would make sense to add a new template, something like
Template:Partitioning_custom_single_blank , which would have the steps:
# Ensure only the single target device you prepared is selected as the
installation target disk.
# Ensure the option to configure partitioning yourself is selected,
and complete this screen.
# On the ''MANUAL PARTITIONING'' screen, delete all existing
partitions (if any).
Then each test case could add the steps unique to itself, e.g.:
|setup=
{{Template:Partitioning_single_setup}}
|actions=
{{Template:Partitioning_actions}}
{{Template:Partitioning_custom_single_blank}}
# Pick 'btrfs' from the ''New mount points will use the following
partitioning scheme:'' drop-down
# Click the ''Click here to create them automatically'' link
# Click ''Done''
# {{Template:Partitioning_actions_post}}
|results=
{{Template:Partitioning_results}}
for the btrfs test case, and:
|setup=
{{Template:Partitioning_single_setup}}
|actions=
{{Template:Partitioning_actions}}
{{Template:Partitioning_custom_single_blank}}
# Pick 'Standard partition' from the ''New mount points will use the
following partitioning scheme:'' drop-down
# Click the ''Click here to create them automatically'' link
# Change the '''File System''' drop-down to ''xfs'', and click
''Update settings''
# Click ''Done''
# {{Template:Partitioning_actions_post}}
|results=
{{Template:Partitioning_results}}
for the XFS test case.
Also, I think maybe we should change
https://fedoraproject.org/wiki/QA:Testcase_upgrade_fedup_cli_previous_desktop
into someone like
https://fedoraproject.org/wiki/QA:Testcase_upgrade_fedup_cli_previous_workstation
and add one
update some test cases
Hi all, I'm intending to modify some test cases in the Fedora test wiki pages,as shown in the following: https://fedoraproject.org/wiki/QA:Testcase_Partitioning_No_Swap How to test Boot the installer using any available means (netinst/boot.iso, PXE, or DVD) on INSTALLATION SUMMARY screen, click into Installation Destination select I will configure partitioning on the Installation Destination page,and proceed with installation On the Manual Partitioning screen, ensure no swap partition is created Complete the installation https://fedoraproject.org/wiki/QA:Testcase_anaconda_ext3_rootfs_on_disk_partition How to test Boot the installer using any available means (netinst/boot.iso, PXE, or DVD) on INSTALLATION SUMMARY screen, click into Installation Destination select I will configure partitioning on the Installation Destination page,and proceed with installation On the Manual Partitioning screen, place the root filesystem(/) on an ext3 formatted partition Complete the installation https://fedoraproject.org/wiki/QA:Testcase_anaconda_xfs_rootfs_on_disk_partition How to test Boot the installer using any available means (netinst/boot.iso, PXE, or DVD) on INSTALLATION SUMMARY screen, click into Installation Destination select I will configure partitioning on the Installation Destination page,and proceed with installation On the Manual Partitioning screen, place the root filesystem(/) on an xfs formatted partition Complete the installation https://fedoraproject.org/wiki/QA:Testcase_anaconda_btrfs_rootfs_on_disk_partition How to test Boot the installer using any available means (netinst/boot.iso, PXE, or DVD) On INSTALLATION SUMMARY screen, click into Installation Destination select I will configure partitioning on the Installation Destination page,and proceed with installation On the Manual Partitioning screen, place the root filesystem(/) on a btrfs formatted partition Complete the installation Also, I think maybe we should change https://fedoraproject.org/wiki/QA:Testcase_upgrade_fedup_cli_previous_desktop into someone like https://fedoraproject.org/wiki/QA:Testcase_upgrade_fedup_cli_previous_workstation and add one for server:Testcase_upgrade_fedup_cli_previous_server Any comments on these will be very welcomed, and as soon as we have a decision on the changes, I will update the wiki page. Thank you, Lili Nie -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Self Introduction: Atmn Patel
- Original Message - From: Atmn Patel atmnpatel.eia...@gmail.com To: test@lists.fedoraproject.org Sent: Monday, December 29, 2014 5:51:15 AM Subject: Self Introduction: Atmn Patel Hello all, My name is Atmn Patel. I am a high school student in a small town near Windsor, ON, Canada. I am technically in grade 10, but I'm looking at a very early graduation. I was going to apply to the University of Toronto this year, but didn't because my parents wouldn't let me go. My dream school is MIT, double major in CS and Physics to pursue a doctorate in Quantum Computing. I started with Linux in grade 6, with Ubuntu (when they still used GNOME) but after they switched to Unity, I changed to Arch Linux. I stuck with Arch until about 10 months ago when I decided that I actually want to start contributing, I changed to Fedora. I spent the last 10 months getting used to it, understanding it, and toying with it, and now I think its time I start contributing. As for my computer skills, I know C and Python to the level of an introductory undergraduate course. I am currently learning Java in my spare time. I am also working towards getting the Linux Foundation Certified System Administrator. As for project experience, I have none. I believe that I am an excellent match for the project because I am willing to learn and dedicate time to the project (I have no experience whatsoever). Time Zone: EST Interests: N/A GPG KEYID and fingerprint: pub 2048R/65B2C7F9 2014-12-28 [expires: 2015-12-28] Key fingerprint = 11E7 A451 66B8 E676 1B70 937E 31A0 9D5F 65B2 C7F9 uid Atmn Patel (Fedora Project) atmnpatel.eia...@gmail.com sub 2048R/ACCE24D7 2014-12-28 [expires: 2015-12-28] -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test Glad to see you brilliant guy here in this list:) As you may know,there are lots of nice professional engineers and I'm sure you will learn a lot during your contribution. Enjoy your time together with Fedora,and I have confidence it will be a life long. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Karma in F20
- Original Message - From: Lili Nie l...@redhat.com To: For testing and quality assurance of Fedora releases test@lists.fedoraproject.org Sent: Tuesday, December 2, 2014 3:19:56 PM Subject: Re: Karma in F20 - Original Message - From: Jonathan Calloway jonathancallo...@gmail.com To: test@lists.fedoraproject.org Sent: Tuesday, December 2, 2014 2:33:46 PM Subject: Karma in F20 Greetings! I was trying to contribute some karma for F20. However, it cannot seem to contact Bodhi. Is it just me? [callowayj@localhost ~]$ fedora-easy-karma Getting list of installed packages... Waiting for Bodhi for a list of packages in updates-testing (F20)... [callowayj@localhost ~]$ Thanks! JC -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test +1 for me. I have added some karmas by visiting the updates web pages, and you can,if you would like to, do the same before the fedora-easy-karma works:) -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test It seems that f21 is also affected here: [lnie@localhost ~]$ fedora-easy-karma Getting list of installed packages... Waiting for Bodhi for a list of packages in updates-testing (F21)... Cannot query Bodhi: ServerError(https://admin.fedoraproject.org/updates/list, -1, Request timed out after 120.0 seconds) [lnie@localhost ~]$ fedora-easy-karma -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Karma in F20
- Original Message - From: Jonathan Calloway jonathancallo...@gmail.com To: test@lists.fedoraproject.org Sent: Tuesday, December 2, 2014 2:33:46 PM Subject: Karma in F20 Greetings! I was trying to contribute some karma for F20. However, it cannot seem to contact Bodhi. Is it just me? [callowayj@localhost ~]$ fedora-easy-karma Getting list of installed packages... Waiting for Bodhi for a list of packages in updates-testing (F20)... [callowayj@localhost ~]$ Thanks! JC -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test +1 for me. I have added some karmas by visiting the updates web pages, and you can,if you would like to, do the same before the fedora-easy-karma works:) -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: 'Nice to have' process is now 'Freeze exception' process, improvements to blocker / freeze exception tracker aliases
Thanks and support+1:). - Original Message - From: Adam Williamson awill...@redhat.com To: test@lists.fedoraproject.org, de...@lists.fedoraproject.org Sent: Tuesday, January 22, 2013 10:30:25 PM Subject: 'Nice to have' process is now 'Freeze exception' process, improvements to blocker / freeze exception tracker aliases Hey folks! At FUDCon Lawrence, Tim Flink presented on the Fedora blocker bug and 'NTH' processes, and we got some interesting and useful feedback. People felt that the 'nice to have' / 'accepted' name used in that process was confusing and difficult to understand, and that the aliases used for the tracker bugs were inconsistent. We developed a proposal to rename the aliases and the 'nice to have' process. This was refined over the period of a few days' discussion on the test@ mailing list: see https://lists.fedoraproject.org/pipermail/test/2013-January/113363.html for the thread. There was a very solid consensus that the old scheme sucked and the final form of the new proposal was miles better, and this is not the first time the topic has come up (there are various proposals in the list archives). So I decided to go ahead and Just Do It, putting the proposal into 'production' today. I have adjusted the tracker bugs themselves, https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Trackers , https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process , https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting , and renamed https://fedoraproject.org/wiki/QA:SOP_nth_bug_process to https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process and adjusted it. I have also made the obvious changes to the relatively large number of other wiki pages that link to and talk about the 'nth' / 'freeze exception' process: see my Wiki edit history for those changes. Here are the practical changes: The 'nice to have' / 'NTH' process is now the 'freeze exception' process: thanks to Jared Smith for the name (though I believe it's actually a resurrection from the old 'freeze exception request' process, which was a better name but a much worse process). This name, very much unlike the other one, 'does what it says on the tin': the freeze exception process is how you request freeze exceptions. Seems pretty simple. 'Freeze exception' is kind of jargon, but it's pretty standard terminology in the tech world, doing a web search for it gives you useful results that explain what it is, as noted it is terminology Fedora has used in the past, and we could not think of a way of concisely expressing the concept in non-jargon English. The 'new style' tracker bug aliases are as follows: AlphaBlocker AlphaFreezeException BetaBlocker BetaFreezeException FinalBlocker FinalFreezeException These names are consistent and, again, 'do what they say on the tin'. We were using aliases ending with -accepted for NTH bugs before, which was a really terrible idea (not least because it meant we used the word 'accepted' in two entirely different ways in one process), and the Final aliases did not follow the same pattern as the Alpha and Beta ones. These primary aliases do not need to be versioned, as Kamil Paral perceptively pointed out: as they are only aliases and can be transferred from bug to bug, we can file a new set of tracker bugs for each release, but transfer these unversioned aliases at the time of each release. So right now these aliases are applied to the F19 trackers: at the time of F19 release, they will be transferred to the F20 trackers. This basically means that, at any point in time, you can simply mark a bug as blocking 'AlphaBlocker' and it will be nominated as blocking the next Alpha release. Versioned aliases will still be applied to all the tracker bugs, so that we can find older ones when we need to and so that a consistent naming scheme is always available for all releases. This format will be used: F18AlphaBlocker F18AlphaFreezeExcept F18BetaBlocker F18BetaFreezeExcept F18FinalBlocker F18FinalFreezeExcept The shortening of 'Exception' to 'Except' is unfortunately forced upon us by a Bugzilla limit of 20 characters for alias names. I have submitted a bug requesting this limit be raised: if this is done, the versioned aliases will be changed to follow the format of the unversioned (FreezeException instead of FreezeExcept). I have not yet filed the Fedora 20 tracker bugs as the text in the tracker bug descriptions refers to these aliases and cannot easily be changed after the bug is filed, so I am waiting to see the resolution of this issue before I file those bugs to ensure accurate text can be included. As our Bugzilla allows for multiple aliases to be applied to bugs, bugs can have both the dynamic aliases and their static aliases applied at once, we can maintain 'backwards compatibility', and old trackers can have the new-style aliases applied to them so you can always use the same naming scheme to find the trackers for any release, even old ones. The Fedora 19 tracker bugs
update some testcases(2)
Hi all, I have taken part in the improve the test wiki pageproposed by Tao Wu. As there is huge change in f18, some test cases in the test wiki pageseem to be inapplicable. I suggest to modify some of them, as the following: Testcase::https://fedoraproject.org/wiki/QA:Testcase_Anaconda_autopart_%28encrypted%29_install How to test Boot the installer using any available means Make sure your disk is set to be encrypted you can encrypt the whole disk before custom partitioning your disk or encrypt part of the disk (for example,/root) after custom partitioning your disk Continue installation with choosing all provided defaults After installation is complete, perform QA:Testcase_base_startup to ensure the installed system boots correctly with the encrypted partitioning Repeat the test, selecting a non-English keyboard map and entering a passphrase which would not be input the same on an English keyboard map Testcase::https://fedoraproject.org/wiki/QA:Testcase_Anaconda_autopart_%28use_free_space%29_install How to test Boot the installer using any available means Make sure your disk is not set to be encrypted Continue installation with choosing all provided defaults， and make sure the existing partitions are not modified As in the text mode, you should choose option of using the free space for the Autopartitioning Options Expected Results The system should install successfully After install, the system initiates boot properly The existing partitions were not modified, the system is installed only into the previously free space. [[QA:Anaconda partitioning#custom|custom partitioning mode]]: Click into Installation Destination, select Continue select Let me custom the partitioning of the disk instead for INSTALLATION OPTIONS select Continue to custom the partition Testcase:: https://fedoraproject.org/wiki/QA:Testcase_Partitioning_No_Swap How to test Boot the installer using any available means (netinst/boot.iso, PXE, or DVD) In the INSTALLATION SUMMARY screen, [[QA:Anaconda partitioning#custom|custom partitioning mode]] At the manual partitioning screen, remove the swap partition created by anaconda, and proceed with installation. Complete the installation Testcase:: https://fedoraproject.org/wiki/QA:Testcase_anaconda_ext3_rootfs_on_disk_partition How to test Boot the installer using any available means (netinst/boot.iso, PXE, or DVD) In the INSTALLATION SUMMARY screen, [[QA:Anaconda partitioning#custom|custom partitioning mode]] At the manual partitioning screen, place the root filesystem(/) on an ext3 formatted partition,and proceed with installation Complete the installation Testcase::https://fedoraproject.org/wiki/QA:Testcase_anaconda_xfs_rootfs_on_disk_partition Boot the installer using any available means (netinst/boot.iso, PXE, or DVD) In the INSTALLATION SUMMARY screen,[[QA:Anaconda partitioning#custom|custom partitioning mode]] At the manual partitioning screen, place the root filesystem(/) on an xfs formatted partition,and proceed with installation Complete the installation Testcase:: https://fedoraproject.org/wiki/QA:Testcase_anaconda_ext4_rootfs_on_disk_partition Boot the installer using any available means (netinst/boot.iso, PXE, or DVD) In the INSTALLATION SUMMARY screen, [[QA:Anaconda partitioning#custom|custom partitioning mode]] At the manual partitioning screen, place the root filesystem(/) on an ext4 formatted partition,and proceed with installation Complete the installation Any comments on these will be welcome, and as soon as we have a decision on the changes, I will update the wiki-page. Thank you, Lili Nie -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: update some testcases
- Original Message - From: Kamil Paral kpa...@redhat.com To: For testing and quality assurance of Fedora releases test@lists.fedoraproject.org Sent: Tuesday, January 8, 2013 3:02:22 AM Subject: Re: update some testcases I think we should create a separate wiki page QA:Anaconda partitioning, that explains the differences between the guided partitioning and custom partitioning, and also between autopart and manual partitioning. Ideally with screenshots. Then we can link that page and simply ask the tester to encrypt the disk using method A or B (or any of them). In this case, I think we only mandate autopart, nothing else. Hi Kamil, I feel a little confused,inguided partitioning mode,we doauto partitiong,incustom partitioning mode,we domanual partitiong, actually,there is no guided partitioning mode orcustom partitioning mode,we do default install then we can call itguided partitiong mode if we change something,we can say it incustom partitiong mode, As for auto partitioning,we only need to clickcontinue.Am I right? Guided mode is the screen where you can only preserve or delete partitions, nothing else. Custom mode is the screen where you can set up the partitions to your will. Automatic partitioning (autopart) is an approach of letting Anaconda create the partition setup automatically for you. It is used in guided mode and _can_ be used in custom mode (by clicking the blue text Create partition layout automatically). Manual partitioning is the approach of doing everything by yourself, basically it is a custom mode without using autopart. I'm using the terms in the sense I see them most often used. But maybe different terms could be less confusing. Adam, do you want to comment on terminology? Hi Kamil, I still feel confused about this.In my mind,we can change mode during one install.ie,if we changed sth we are in so called custom mode,after that, if we click the blue text Create partition layout automatically we are in Guided mode then.We can also change the mode to custom mode by changing sth after we are in Guided mode. If something is not explicitly stated in the test case, people should be free to do it as they see fit. We might set up some testing introduction page and describe these principles. But I agree with you, in order to encourage using different keymaps, we can explicitly say it's allowed. That's why I proposed: We can explicitly say the password _might not_ be set using an English keymap. However,if we say the password_might not_be set using an English keymap, people will using a non-English keymap.Then the English one will not be tested. Yes, that's basically the same. I prefer to not quote the button labels (option for using the free space instead of choose 'use free space'). yeah,that's better. Thanks for your work. When you're at it, could you please try to create the QA:Anaconda partitioning wiki page with a few screenshots and a short description what guided partitioning mode, custom partitioning mode, auto partitioning, and manual partitioning are? I believe that would be very useful for lots of our test cases. Then we can update some of them with links as proposed above. Thanks a lot for your comments .But,er..it seems that there is no need to take sreenshot,as the anaconda's explanation is clear enough. I imagine a page with a screenshot of guided mode screen, and a screenshot of custom mode screen. It would be used to illustrate what is the guided mode and what is the custom mode. There doesn't need to be a lot of description, just saying this is the guided mode and this is the custom mode is enough. We can then link the page, people will have a look at it and in 10 seconds they will understand which parts of anaconda they should work with to verify the test case. Actually,what I concerned is that,there are so many guided mode screen and custome mode screen during one install,what's more, that's what people can see immediately they click the button. Thanks for working on this. It's my pleasure.Actually,it's what I should do:) -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: update some testcases
- Original Message - From: Adam Williamson awill...@redhat.com To: For testing and quality assurance of Fedora releases test@lists.fedoraproject.org Sent: Tuesday, January 8, 2013 3:22:18 PM Subject: Re: update some testcases On Tue, 2013-01-08 at 03:02 -0500, Kamil Paral wrote: I'm using the terms in the sense I see them most often used. But maybe different terms could be less confusing. Adam, do you want to comment on terminology? That's how I've been doing it so far. It feels like we could somehow come up with better names, but no-one has yet :) The dialog which pops up after you select disks for installation - and either says 'You have enough space, you're all set!' or 'You don't have enough space, you need to free some up!' - is the branch point for 'Guided' vs. 'Custom' install. Both versions of that dialog have a checkbox whose label says something about 'Customize the layout'. If you check that checkbox and then proceed from the dialog, you are now in the 'custom partitioning' flow. If you leave the checkbox unchecked and proceed from the dialog, you are now in the 'guided partitioning' flow. If you had enough space, and you don't check the box, then you are now done with partitioning, there is no further screen in the flow - but we still refer to it as the 'guided partitioning' flow. As kparal says, the 'autopart' algorithm can actually be invoked from each path. 'Guided partitioning' always uses the 'autopart' algorithm to actually create the final partition layout. In 'custom partitioning' you can choose to use it, by clicking the 'Create partition layout automatically' text Kamil mentioned. Or you can choose not to use it, and to actually create each partition manually. I probably wouldn't want to try and use the term 'manual partitioning' to mean 'custom partitioning without using the 'autopart' link', that seems unnecessarily confusing - really, 'custom partitioning' is still 'custom partitioning' whether you clicked the 'autopart' link or not. Hi Adam,the custom mode and the autopart mode is clear enough for me .What confused me is that I thought we are in autopart mode as long as we change nothing and just do default things, we are in custom mode the moment we change sth.That's why I say we can change mode for several times during one install. No, that's still custom mode. As long as you're in the custom dialog,you're in custom mode. The 'Create partition layout automatically'function is just a little helper.make it clear at once,and I don't feel confused now:)thanks for your comment. In the original text there is also: # Repeat the test, selecting a non-English keyboard map and entering a passphrase which would not be input the same on an English keyboard map Personally I would erase this one, I'm not a fan on repeat-several-times test cases. We can explicitly say the password _might not_ be set using an English keymap. It's then up to people to choose. In several test runs we will receive the same result (multiple keymaps tested) with less time invested. For this one ,I'm a little disagree with you.If we do not highlightselecting a non-English keyboard map，we QA may tends to use English keyboard map only. for example,I am an Chinese,but I would just do the default English install for all the testcases,if there is no special saying. If something is not explicitly stated in the test case, people should be free to do it as they see fit. We might set up some testing introduction page and describe these principles. But I agree with you, in order to encourage using different keymaps, we can explicitly say it's allowed. That's why I proposed: We can explicitly say the password _might not_ be set using an English keymap. So the reason this case is as it is right now is that when the issue of keymap problems first came up, I considered writing separate 'keymap' test cases, but it seemed a bit artificial: the 'non-US keymap encrypted partitioning test case' would have been a copy/paste of the encryption test case, but with 'use a non-US keymap' added. Seemed a bit silly, and it didn't seem that hard just to add it into the existing test case. While you're testing encryption, you may as well make sure it works with a non-US keymap too. The reason for saying to run the test twice, once with a US keymap and once without, is to make it easier to tell whether a failure is due to the use of a non-US keymap or not: if you just use a non-US keymap, and you get a failure, it's hard to know whether it's a general failure, or because you're using a non-US keymap. If you run the test twice, it should make it relatively clear what causes any failure. There are more efficient ways of doing things, but they're harder to explain in a test case. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To
Re: update some testcases
How to test Boot the installer using any available means (netinst/boot.iso, PXE, or DVD) Click into Installation Destination, select Let me custom the partitioning of the disk instead,select Continue At the manual partitioning screen, choose root and click Customize Place the root filesystem(/) on an ext3 formatted partition,and select Finish Partitioning Complete the installation Similar to above. Again, let's try to keep the instructions generic if the functionality is obvious. There is no need to say click Customize. We can simply say change the root (/) file system to ext3. If some one is unable to figure out the approach, he/she won't be able to fill in bugzilla report anyway. We don't target complete Linux newbies here. Testcase::https://fedoraproject.org/wiki/QA:Testcase_anaconda_xfs_rootfs_on_disk_partition Boot the installer using any available means (netinst/boot.iso, PXE, or DVD) Click into Installation Destination, select Let me custom the partitioning of the disk instead,select Continue At the manual partitioning screen, choose root and click Customize Place the root filesystem(/) on an xfs formatted partition,and select Finish Partitioning Complete the installation Same as above. Testcase:: https://fedoraproject.org/wiki/QA:Testcase_anaconda_ext4_rootfs_on_disk_partition Boot the installer using any available means (netinst/boot.iso, PXE, or DVD) Click into Installation Destination, select Let me custom the partitioning of the disk instead,select Continue At the manual partitioning screen, choose root and click Customize Place the root filesystem(/) on an ext4 formatted partition,select Standard Partition for Device type Select Finish Partitioning，and Complete the installation Same as above. Any comments on these will be welcome, and as soon as we have a decision on the changes, I will update the wiki-page. Thank you, Lili Nie Thanks for your work. When you're at it, could you please try to create the QA:Anaconda partitioning wiki page with a few screenshots and a short description what guided partitioning mode, custom partitioning mode, auto partitioning, and manual partitioning are? I believe that would be very useful for lots of our test cases. Then we can update some of them with links as proposed above. Thanks a lot for your comments .But,er..it seems that there is no need to take sreenshot,as the anaconda's explanation is clear enough. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
update some testcases
Hi all, I have taken part in the improve the test wiki pageproposed by Tao Wu. As there is huge change in f18, some test cases in the test wiki pageseem to be inapplicable. I suggest to modify some of them, as the following: Testcase::https://fedoraproject.org/wiki/QA:Testcase_Anaconda_autopart_%28encrypted%29_install How to test Boot the installer using any available means Make sure your disk is set to be encrypted you can encryted the whole disk before custom partitioning your disk or encryted part of the disk (for example,/root) after custom partitioning your disk Select the appropriate disk, and continue installation, choosing all provided defaults After installation is complete, perform QA:Testcase_base_startup to ensure the installed system boots correctly with the encrypted partitioning Testcase::https://fedoraproject.org/wiki/QA:Testcase_Anaconda_autopart_%28use_free_space%29_install How to test Boot the installer using any available means Make sure your disk is not set to be encrypted Select the appropriate disk, and continue installation, choosing all provided defaults As for the text mode, you should chooseuse free spacefor the Autopartitioning Options Complete the installation Testcase:: https://fedoraproject.org/wiki/QA:Testcase_Partitioning_No_Swap How to test Boot the installer using any available means (netinst/boot.iso, PXE, or DVD) Click into Installation Destination, select Let me custom the partitioning of the disk instead,select Continue At the manual partitioning screen, remove the swap partition created by anaconda, and select Finish Partitioning Complete the installation Testcase:: https://fedoraproject.org/wiki/QA:Testcase_anaconda_ext3_rootfs_on_disk_partition How to test Boot the installer using any available means (netinst/boot.iso, PXE, or DVD) Click into Installation Destination, select Let me custom the partitioning of the disk instead,select Continue At the manual partitioning screen, choose root and click Customize Place the root filesystem(/) on an ext3 formatted partition,and select Finish Partitioning Complete the installation Testcase::https://fedoraproject.org/wiki/QA:Testcase_anaconda_xfs_rootfs_on_disk_partition Boot the installer using any available means (netinst/boot.iso, PXE, or DVD) Click into Installation Destination, select Let me custom the partitioning of the disk instead,select Continue At the manual partitioning screen, choose root and click Customize Place the root filesystem(/) on an xfs formatted partition,and select Finish Partitioning Complete the installation Testcase:: https://fedoraproject.org/wiki/QA:Testcase_anaconda_ext4_rootfs_on_disk_partition Boot the installer using any available means (netinst/boot.iso, PXE, or DVD) Click into Installation Destination, select Let me custom the partitioning of the disk instead,select Continue At the manual partitioning screen, choose root and click Customize Place the root filesystem(/) on an ext4 formatted partition,select Standard Partition for Device type Select Finish Partitioning，and Complete the installation Any comments on these will be welcome, and as soon as we have a decision on the changes, I will update the wiki-page. Thank you, Lili Nie -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Non-English installs of F18 Beta TC7 broken
1)I have default install in Chinese and French,the crash did not happen. 2)When I try to install it in Italian and Place the root filesystem(/) on a xfs formatted partition,the crash happend. 3)Then I try 2) in Chinese and French,both are crashed. - Original Message - From: Adam Williamson awill...@redhat.com To: test@lists.fedoraproject.org Sent: Sunday, November 4, 2012 5:40:16 AM Subject: Non-English installs of F18 Beta TC7 broken Hey, folks. There appears to be a confirmed bug breaking installs in many (maybe all) non-English installs of Beta TC7: https://bugzilla.redhat.com/show_bug.cgi?id=872791 this is likely related to various patches that went into TC7 to improve language selection. The anaconda devs will get on it ASAP, but in the meantime, we can still do most of the validation testing - just use English for your tests for now. Sorry for the inconvenience, non-native English speakers :) -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
