Goal

kubevirt compute e2e tests should not depend on libdomain.GetRunningVMIDomainSpec or libdomain.GetRunningVirtualMachineInstanceDomainXML unless absolutely necessary

User Stories

• As a KubeVirt developer, I want to find my end-to-end tests to test API behavior, not implementation details. Implementation details such as libvirt's domain XML/Spec should be tested in unit tests.

Non-Requirements

• List of things not included in this epic, to alleviate any doubt raised during the grooming process.

Notes

• Specifically,
  $ git grep libdomain
  .| wc -l
  68
  should be zero or next-to-zero.
•  I believe that every usage of `GetRunningVMIDomainSpec` is a code smell, signifying one or more of:
  • an e2e test that should be converted to a unit test
  • an e2e test that does not cover the user story
  • a missing KubeVirt API