Ticket #263 (closed task: fixed)

Opened 2 years ago

Last modified 23 months ago

Expand Xen test case set

Reported by: adamwill Owned by: tflink
Priority: major Milestone: Fedora 17
Component: Wiki Version:
Keywords: Cc:
Blocked By: Blocking:


After checking with the Xen experts on list, it became clear that it would be a good idea to somewhat improve and extend our set of Xen test cases:


Konrad Wilk summarizes:

"It would be nice to expand the tests, and it kind of boils down to:

1) Does it boot 2) Does it work

The complexity is that there are three modes of this: HVM (so similar to the KVM test-case), PV (we got that covered now), and the Dom0 (which is mostly - does it boot and you kind of implicitly need to do this before you can do the other two).

So I think it makes sense to add the HVM case in the test-matrix - it is pretty simple and similar to the KVM one.

The dom0 is a bit more complex, but we already have it outlined in the http://fedoraproject.org/wiki/Features/XenPvopsDom0 in the Documentation part - so it should be fairly easy to lift it out of there. (adn the stuff about the bridge is not needed anymore)."

If someone with knowledge of the area could take this ticket and draft up the set of proposed test cases then mail them to the list for discussion, that would be great. Thanks!

Change History

comment:1 Changed 2 years ago by adamwill

  • Owner set to tflink

comment:2 Changed 2 years ago by tflink

I'm trying to get this taken care of but I'm still a bit fuzzy on the purpose here. Are we trying to improve our test cases around the final release requirement for Xen DomU or are we trying to improve our general test case coverage to be more than the very specific Xen DomU test cases and the very generic Xen PV DomU installation test case?

comment:3 Changed 2 years ago by konradr

Oh, had not seen the very specific Xen DomU test-cases. Those are quite good! I think it would make sense to stick them under the https://fedoraproject.org/wiki/QA:Testcase_Boot_Methods_Xen_Para_Virt and naturally update the very specific ones.

comment:4 Changed 2 years ago by adamwill

For me the priority is to ensure we have whatever we need in the matrix to 'enforce' the release criterion. If that's just a single test case that's fine, just need to make sure it's complete, easy to follow, and up to date.

Further test cases are nice but that's a secondary priority.

comment:5 Changed 2 years ago by tflink

I think that the PV test case we have now is enough to cover the release requirements since I don't think that the Xen based cloud providers support HPV.

I think that it would be nice to move Dom0 setup instructions from the F16 feature page since I imagine that most people would be testing with Fedora but I don't think that is absolutely needed and the HPV test case is more of a NTH general case and not required for the release requirements.

comment:6 Changed 23 months ago by adamwill

  • Resolution set to fixed
  • Status changed from new to closed

I think this is sufficiently covered now, everyone seems happy with the test we have in the matrix. Closing.

Note: See TracTickets for help on using tickets.