#16: Create Installer repo test(s)
--------------------------+-------------------------------------------------
Reporter: jlaska | Owner: rhe
Type: task | Status: new
Priority: minor | Milestone: Fedora 13
Component: Test Review | Version:
Resolution: | Keywords:
--------------------------+-------------------------------------------------
Comment (by jlaska):
Replying to [comment:13 rhe]:
> Replying to [comment:10 jlaska]:
> > * 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
>
> I've modified the test cases for covering these 2 points.
Nice work, that helps make the tests more explicit.
> > * 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 can see that you want to make the test cases cover more conditions.
But here I agree with Liam that if we do so, the test cases may have too
much possible conditions and look very wired. I think we design general
cases to serve our need and that's ok.
Yeah, you two make a good point. Always a balance trying to figure out
how much to stuff into a single test. Besides, the list of steps above
are really corner case type issues.
> So I improved especially mirrorlist repo case and now we have covered
the following items:
>
> 1. Check the existing repos listed in the screen.
> 2. Provide new repo address by Add/modify buttion to have additional
one.
> 3. The method includes HTTP/FTP, CD/DVD, NFS.
> 4. Verify them in next screen and after reboot.
> >
> > 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]).
>
> I've made some experiments on my pc by setting up a local apache to test
it. It works but I don't know how to host them on fedorapeople.org pages
for everyone to use. Is it very tough? :)
Yeah, you should have access to create a fedorapeople.org page. Take a
look at http://fedoraproject.org/wiki/Infrastructure/fedorapeople.org for
access information.
If you're able to create a small sample repo, with some dummy packages
that can be used for producing consistent test results ... it might not be
a bad thing to try. Possibly overkill, and I don't know if this might be
helpful for your repo needs, but checkout
https://fedorahosted.org/rpmfluff/ for a quick way to build packages that
meet specific criteria (name, version, release).
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/16#comment:15>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
--
test mailing list
test@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
