|
|
| (112 intermediate revisions by 4 users not shown) |
| Line 1: |
Line 1: |
| Fedora Test Day - Encrypted Block Device Installation
| | {{draft}} |
|
| |
|
| = WHAT = | | === DVD === |
|
| |
|
| It's time to kick the tires on encrypted block device installation support in F10-Alpha. There have been several changes on this front recently, most notably the arrival of [http://fedoraproject.org/wiki/Features/BetterStartup plymouth]. The plan is meet and try to poke holes in encrypted block device installations. We'll have a host of QA and Development characters hanging out discussing bugs (aka "features"), expectations, and test areas. I've included details below for how you can contribute below.
| | {| class="wikitable collapsible" border="1" width="85%" |
| | | |- |
| = WHEN = | | ! colspan="5" style="background-color: pink;" | DVD.iso installation |
| | | |- |
| '''DATE:''' Thursday, August 14th, 2008
| | | |
| | | {| class="wikitable sortable" width=100% style="border: solid 2px white" |
| '''TIME:''' Between ''12:00'' and ''21:00'' UTC (8am -> 5pm EDT)
| | |- |
| | | ! width="20%"|Release Level !! width="15%"|Test Area !! width="45%"|Test Case !! width="10%"|i386 !! width="10%"|x86_64 |
| = WHERE = | | |- |
| | | | Alpha |
| Discussion will be held on IRC in the [irc://irc.freenode.net/fedora-qa #fedora-qa] channel. There are quite a few different IRC clients out there you can use to join the discussion, including:
| | | Image Sanity |
| | | | [[QA:Testcase_Mediakit_ISO_Size]] |
| * Web-based mibbit (no additional software required)- [http://embed.mibbit.com/?server=irc.freenode.net&channel=%23fedora-qa&forcePrompt=true join #fedora-qa]
| | | {{result|pass}} {{result|pass}} |
| * Chatzilla firefox extension - [https://addons.mozilla.org/firefox/16/ install Chatzilla]
| | | {{result|pass}} {{result|pass}} |
| * A slew of popular linux clients - http://www.ircreviews.org/clients/platforms-unix.html
| | |- |
| | | | Alpha |
| = WHY = | | | Image Sanity |
| | | | [[QA:Testcase_Mediakit_ISO_Checksums]] |
| Have you tried installing using an encrypted block device yet? Support for installing to encrypted block devices was added in Fedora 9 (see https://fedoraproject.org/wiki/Anaconda/Features/EncryptedBlockDevices). While this support has been present for an entire release, it hasn't yet been given a thorough test review. Additionally, with the presence of [http://fedoraproject.org/wiki/Features/BetterStartup plymouth], the method by which unlocking your encrypted devices has changed dramatically.
| | | {{result|pass}} |
| | | | {{result|pass}} |
| It's the new hotness and it could use your help in identifying use cases and fleshing out defects.
| | |- |
| | | | Alpha |
| = WHO = | | | Image Sanity |
| | | | [[QA:Testcase_Mediakit_Repoclosure]] |
| The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...
| | | {{result|pass|robatino}} {{result|pass|kparal}} |
| * dlehman
| | | {{result|pass}} {{result|pass}} |
| * halfline
| | |- |
| * jlaska
| | | Alpha |
| * bo09
| | | Image Sanity |
| * atodorov
| | | [[QA:Testcase_Mediakit_FileConflicts]] |
| * rwilliam
| | | {{result|pass}} {{result|warn}} |
| * mganisin
| | | {{result|pass}} {{result|pass}} |
| | | |- |
| If you'd like to sign up to help field questions, please add your name to the list above.
| | | Alpha |
| | | | Boot Methods |
| = HOW =
| | | [[QA/TestCases/BootMethodsDvd]] |
| | | | {{result|pass}} {{result|pass}} |
| There are many ways you can help, depending on your interests and skill level.
| | | {{result|pass}} {{result|pass}} |
| | | |- |
| == Triage NEW Bugs ==
| | | Alpha |
| | | | Install Source |
| Much like a field hospital, bug triage describes the art of quickly addressing the big issues in a bug, and moving it on for further review by the development team. Unlike a field hospital, there ''should'' be no blood or gunfire. The triage process has generated quite a following. As outlined on the [[BugZappers]] home, triage is a several step process:
| | | [[QA/TestCases/InstallSourceDvd]] |
| | | | {{result|pass}} {{result|pass}} |
| # [[BugZappers/GettingStarted| Getting started]]
| | | {{result|pass}} {{result|pass}} |
| # [[BugZappers/FindingBugs| Finding bugs to triage]], the list we'll use for Test Day includes:
| | |- |
| #* List of ''NEW'' installer encrypted block device bugs needing triage: http://tinyurl.com/6k8e5h
| | | Alpha |
| #* List of ''NEW'' Plymouth bugs: http://tinyurl.com/6omrxn
| | | Repository |
| # [[BugZappers/TakingAction| Taking action]]
| | | [[QA:Testcase Additional Http Repository]] |
| | | | {{result|pass|jlaska}} |
| One should not spend more than 5 minutes triaging a single bug. If you have more time to spare, and are looking to get a bit more involved, please proceed with ''Bug Verification'' or ''Test Execution''.
| | | {{result|pass|mkrizek}} |
| | | |- |
| == Verify Bug Fixes ==
| | | Alpha |
| | | | Repository |
| At this time there are no unverified bug fixes. However, that will likely change as the days go on.
| | | [[QA:Testcase Additional Ftp Repository]] |
| | | | {{result|fail}} |
| * Encrypted block device installation ''MODIFIED'' bugs - http://tinyurl.com/5eklvb
| | | {{result|warn}} |
| * Plymouth ''MODIFIED'' bugs - http://tinyurl.com/5pf37f
| | |- |
| | | | Alpha |
| {{admon/important|FIXME|Do we need details, perhaps just a small list | | | Repository |
| # Visit a list of bugs '''here'''
| | | [[QA:Testcase Additional Mirrorlist Repository]] |
| # Update
| | | {{result|pass}} |
| # Select a bug to verify
| | | {{result|pass}} |
| # Each bug should outline steps to reproduce
| | |- |
| # If you have followed those steps, and are unable to reproduce the failure, move to CLOSED RAWHIDE
| | | Beta |
| }} | | | Repository |
| | | | [[QA:Testcase Additional NFS Repository]] |
| {{admon/note | ADD THIS | Give people an idea of what they need to verify bugs, like: | | | {{result|pass}} |
| # A system running ''{Rawhide?, Fedora 10 Alpha?}''
| | | {{result|pass}} |
| #* If VM will work, give instructions on how anyone can do this from soup to nuts, somewhere.
| | |- |
| #* If not, tell them where to get Rawhide boot media and point them at the Installation Guide
| | |} |
| # A browser (preferably on a separate computer, or the VM host?)
| | |} |
| # Requires more time investment than bug triage, but still easy to do
| |
| }} | |
| | |
| == Exploratory Testing ==
| |
| | |
| Exploratory testing is an approach to software testing that is not scripted or planned in as much detail as a more traditional test plan. Rather than walking through a series of pre-defined test cases, the tester is asked to think about the high-level test areas in the software. From there, the tester is encouraged to use their knowledge of the product and the code in order to navigate through different areas of the software. As they walk through the software, their emphasis is to find bugs, expose new test areas, and learn more about the product to help guide future test efforts.
| |
| | |
| The simplest definition from [http://www.satisfice.com/articles/et-article.pdf Exploratory Testing Explained by James Bach] works the best:
| |
| | |
| ''Exploratory testing is simultaneous learning, test design, and test execution.''
| |
| | |
| For further reading on exploratory testing can be found at http://en.wikipedia.org/wiki/Exploratory_testing.
| |
| | |
| === Test Areas ===
| |
| For our test day, let's define the following test areas as primary focus areas for exploratory testing:
| |
| | |
| # '''Software [http://en.wikipedia.org/wiki/Redundant_array_of_independent_disks RAID]''' - mix encrypted raid devices, raid members
| |
| # '''[http://en.wikipedia.org/wiki/Logical_volume_management LVM]''' - physical volumes, logical volumes
| |
| # '''File system probing''' - Scanning a filesystem that may, or may not, contain encrypted block devices (includes rescue-mode)
| |
| # '''Rescue mode''' - can we find and use encrypted devices?
| |
| # '''Passphrase prompt''' - anything related to passphrase prompting, different keyboards, languages, hitting <back> or <cancel> several times
| |
| # '''SELinux''' - different policies, permissive, enforcing ... does this affect storing or checking the passphrase?
| |
| | |
| == Targeted Testing ==
| |
| | |
| Not in the mood for exploratory testing? That's fine. We've taken the time to define explicit test cases for the different test areas noted above.
| |
| | |
| How you can help:
| |
| | |
| === Test execution ===
| |
| | |
| With a spare system(s) in hand, you are welcome to walk through one or more of the following test cases.
| |
| | |
| * Encrypted block device installation tests cases - https://fedoraproject.org/wiki/Anaconda/Features/EncryptedBlockDevices#Test_Plan
| |
| * Plymouth test cases - http://fedoraproject.org/wiki/Features/BetterStartup#Test_Plan
| |
| | |
| The goal is to flesh out any bugs in the software that might be exposed by your special hardware environment.
| |
| | |
| {{admon/important|Data May Be Destroyed|Any time you are testing installation, it is tremendously easy to reformat all partitions on your drive, thus loosing all data. Before proceeding, ensure your data is backed up.}} | |
| | |
| === Test review ===
| |
| | |
| See a typo in the proposed test matrix? Have an interesting hardware scenario to share? Is something not clear? Help us improve the test coverage.
| |
| | |
| Come join us on #fedora-qa, ask questions, propose changes, and share your issues.
| |
| | |
| = Known Issues =
| |
| | |
| Both encrypted block device installation, and plymouth have been available for testing already. As a result, there is a list of bugs already filed for each area. Before you file a new bug, please refer to the following before filing a new bug:
| |
| | |
| * Plymouth known issues - http://tinyurl.com/5euz7s
| |
| * Installer encrypted block devices known issues - http://tinyurl.com/5wwt3y
| |
