Re: update some testcases(2)
On Mon, 2013-01-14 at 01:16 -0500, Lili Nie wrote: Thanks a lot Kamil and Adam for their comments. Welcome more comments and as soon as we have a decision on the changes,the wiki-page will be updated. You don't necessarily need a 'decision' - the convention is that you propose your changes, then if you get any feedback, deal with the feedback, then keep doing that cycle until one of two things happen: 1) you get all 'positive' feedback, no suggested changes 2) you stop getting any feedback at all if you propose a change and don't get any feedback on it within a couple of weeks, and you're pretty sure it's a sensible change, it's fine to just go ahead and do it. 'No complaints' counts as 'approval'. :) It's always a wiki, things can always be changed if someone comes along and sees a problem later. If you propose something and no-one goes 'no! that's terrible!' within two weeks, it's a pretty good indication your change at least isn't just completely terrible. -- 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
Re: update some testcases(2)
Thanks for lnie's updates, if you have any suggestions, just let us known as soon as possible. Any comment is welcomed! Thanks! On 13-01-10 01:52, Lili Nie wrote: 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 -- Best Regards, Tao Wu -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
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
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? 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. 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 This test case is a bit unclear that only the free space should be used. I think this would do: # Install Fedora into the existing free space, without modifying the existing partitions. That should be the default behavior of graphical installer when you select the target disk and follow the default choices. In text mode, there is a special option for using the free space. For this,we can add one sentence: 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， and make sure the existing partitions are not modified As for the text mode, you should chooseuse free spacefor the Autopartitioning Options 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'). 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
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
On Tue, 2013-01-08 at 03:02 -0500, Kamil Paral wrote: 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? 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. 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
Re: update some testcases
From: Adam Williamson awill...@redhat.com Sure, but then you've just switched modes. The decisions you made on the Guided path are wiped out. This could be made clearer in the UI, though - I've seen several users report that they expected to be able to, say, delete partitions in Guided mode, then create them in Custom mode. I did that just today with my desktop machine. I wanted to leverage the Guided feature for most of the setup, but needed to rm the home partition since I have that via NFS. To me the existing naming seemed fairly clear. In a Guided mode, I expect to have the way led for me, but I should be allowed to deviate. With a Manual mode I expect to lead the way, but also be offered tools to make that easier. I guess I didn't think of it so much as modes though, as much of a initial question of how much assistance was I going to require. PS. I may have all the names horfed up here. I've only used the new anaconda this once. I've installed F18 hundreds of times already, but always via kickstarts ala livecd-tools. -- John Florian -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: update some testcases
On Tue, 2013-01-08 at 15:49 -0500, john.flor...@dart.biz wrote:
From: Adam Williamson awill...@redhat.com
Sure, but then you've just switched modes. The decisions you made on
the
Guided path are wiped out. This could be made clearer in the UI,
though
- I've seen several users report that they expected to be able to,
say,
delete partitions in Guided mode, then create them in Custom mode.
I did that just today with my desktop machine. I wanted to leverage
the Guided feature for most of the setup, but needed to rm the home
partition since I have that via NFS.
To me the existing naming seemed fairly clear. In a Guided mode, I
expect to have the way led for me, but I should be allowed to
deviate. With a Manual mode I expect to lead the way, but also be
offered tools to make that easier. I guess I didn't think of it so
much as modes though, as much of a initial question of how much
assistance was I going to require.
Thinking of it as 'modes' is more kind of a tool for debugging / QA, so
far as the 'UI experience' goes, it is actually meant to 'look' more the
way you thought of it ('how much assistance am I going to require'). But
for QA / dev purposes, it's most helpful to keep a sort of mental map of
all the possible workflows / modes in anaconda, and understand that the
whole partitioning step is kind of a mini-wizard mode with two major
branches ('guided' and 'custom').
--
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
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
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: Thursday, January 3, 2013 6:43:15 AM Subject: Re: update some testcases 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 The sentence above is the only change I see from the original text (please note the correct word is to encrypt). 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? 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 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. 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 Instead of updating these instructions in every test case for every anaconda string change, this should link to QA:Anaconda partitioning. That would be just a single page to keep updated. Then we can provide generic instructions: # In the partitioning screen, enter the [[QA:Anaconda partitioning#custom|custom partitioning mode]] and have the installer set up a [[QA:Anaconda partitioning#autopart|default partitioning layout]]. # Remove swap partition from the default layout. # Proceed with installation. I think it's a good suggestion,and I will try to modify the testcases in this way 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 This test case is a bit unclear that only the free space should be used. I think this would do: # Install Fedora into the existing free space, without modifying the existing partitions. That should be the default behavior of graphical installer when you select the target disk and follow the default choices. In text mode, there is a special option for using the free space. For this,we can add one sentence: 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， and make sure the existing partitions are not modified As for the text mode, you should chooseuse free spacefor the Autopartitioning Options And we should have one more expected result: # The existing partitions were not modified, the system is installed only into the previously free space. Yeah,we should add this into the expected result Testcase:: https://fedoraproject.org/wiki/QA:Testcase_anaconda_ext3_rootfs_on_disk_partition
Re: update some testcases
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 The sentence above is the only change I see from the original text (please note the correct word is to encrypt). 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. 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 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. 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 This test case is a bit unclear that only the free space should be used. I think this would do: # Install Fedora into the existing free space, without modifying the existing partitions. That should be the default behavior of graphical installer when you select the target disk and follow the default choices. In text mode, there is a special option for using the free space. And we should have one more expected result: # The existing partitions were not modified, the system is installed only into the previously free space. 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 Instead of updating these instructions in every test case for every anaconda string change, this should link to QA:Anaconda partitioning. That would be just a single page to keep updated. Then we can provide generic instructions: # In the partitioning screen, enter the [[QA:Anaconda partitioning#custom|custom partitioning mode]] and have the installer set up a [[QA:Anaconda partitioning#autopart|default partitioning layout]]. # Remove swap partition from the default layout. # Proceed with 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 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
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: update some testcases
I am happy to see some changes in the test wiki page, and expecting for your feedback. Thanks! On 12-12-28 04:38, Lili Nie wrote: 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 -- Best Regards, Tao Wu -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
