Greetings folks, Liam Li is designing several new test cases [1] to validate yum repo management during the installer. The QA team currently does not have test coverage for these dialogs and is looking to get some basic sanity tests in place for F-13. The question came up as to whether we need to verify that additional custom repositories are present on the installed system. In Liam's testing, it appears that the repositories are only for install-time, not for the post-installed system. Is this accurate? Are there exceptions to this? Thanks, James [1] https://fedorahosted.org/fedora-qa/ticket/16
--- Begin Message ---
- Subject: Re: [Fedora QA] #16: Create Installer repo test(s)
- From: "Fedora QA" <trac@xxxxxxxxxxxxxxxx>
- Date: Tue, 05 Jan 2010 06:01:26 -0000
- Delivered-to: jlaska@xxxxxxxxxxxxxxxxx
- In-reply-to: <051.9354ff8976d318a2b86e1923945bec4b@xxxxxxxxxxxxxxxx>
- References: <051.9354ff8976d318a2b86e1923945bec4b@xxxxxxxxxxxxxxxx>
- Reply-to: nobody@xxxxxxxxxxxxxxxxx
#16: Create Installer repo test(s) --------------------------+------------------------------------------------- Reporter: jlaska | Owner: liam Type: task | Status: new Priority: minor | Milestone: Fedora 13 Component: Test Review | Version: Resolution: | Keywords: --------------------------+------------------------------------------------- Comment (by liam): Replying to [comment:10 jlaska]: > > I guess I'm not sure what expectations there are for how the customized install repos are reflected on the installed system. So as you mention, if I add a new repo during the install screen, does that repo exist in ''/etc/yum.repos.d/anaconda.repo'' after install? After tested,there is no /etc/yum.repos.d/anaconda.repo in installed system when added a repo during install. > In general the tests look great, thanks for taking initiative to make these suggested improvements :) > > I think you've captured the different target repos (CD/DVD, ftp, http, nfs) allowed by anaconda nicely. Some general thoughts noted below, let me know if any of these are off base, or don't apply: > > Since yum repos can include additional metadata on package groups (aka comps.xml), perhaps we should consider: > * modifying the tests so that they also verify whether the expected packages or package groups provided by the custom yum repos appear on the subsequent package detail screen. > * also, updating the tests to confirm that you can select a package provided by the added yum repo and ensure it's selected and installed as expected Very good suggestion, I will modify cases to cover that > * I think each test might also add the following instructions to confirm all create/modify/delete operations work on the added repos. > 1. Add a new yum repo using the recommended method (CD/DVD, http, nfs etc...) > 1. Remove the created repo > 1. Add it again ... then modify the repo (changing the name) > 1. Enable and disable the created repository I considered that before,if put all the specific step in cases, the cases will become more. Just like the partition cases,if the New/Edit/Delete/Reset all write as a case,there will be so many.But what you said is also important,I will try to add these operations to cases. > To accomplish the first 2 points, we may need to create several sample yum repos (hosted on one of our fedorapeople.org pages) that provides the needed conditions to satisfy the tests. The command {{{createrepo -g comps.xml /path/to/packages}}} can be used to create a yum repo with package groups. The comps.xml file used with FEdora is included in the repodata directory (see [http://download.fedora.redhat.com/pub/fedora/linux/releases/12/Fedora/x86_64/os/repodata/6a72ae27742d1b4ac04f2eec0e5ffb0b7c909d58b9c6e346a7ee5cfb627832d4-Fedora-12-comps.xml comps.xml]). If we uncheck the current installation repo and provide a full repo to complete installation. I mean we do not use the current default repo,but use provided repo to finish installation,does this make sense to complete your first 2 points? I am not sure whether the testers can distinguish added repo packages from default repo -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/16#comment:11> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance
--- End Message ---
Attachment:
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Anaconda-devel-list mailing list Anaconda-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/anaconda-devel-list
