Re: [Tails-dev] automated tests

bertagaz@??? wrote (20 Jun 2012 09:52:20 GMT) :
>> (In the setup we had in mind for the upcoming autobuild/autotest
>> server, the builds and tests would be started from different systems,
>> due to incompatibility between the VirtualBox and KVM kernel modules.)

> Probably because I didn't know or forgot this part of the specs. :)

OK :)

> You mean we can't build Tails inside a kvm domain because then
> virtualbox has trouble installing?

No. Fortunately, Tails builds perfectly inside a KVM domain :)

But, given:
- we want to run our automated builds using Vagrant, which implies:
the build system must have the VirtualBox kernel modules loaded
- we want to run our automated tests using KVM (better supported by
libvirt, USB 2.0 support), which implies: the testing system must
have the kvm kernel module loaded
- on a given system, one cannot load the "kvm" and "vbox*" kernel
modules at the same time

=> the testing and build systems must be different systems.

In practice, both the build and testing systems will likely be KVM
domains running on a bare-metal host. We'll need nested virtualization
enabled for kvm_intel on this bare-metal host.

> But well, basically all that this cucumber tests need are an iso
> file, and its path can be configured by the ISO env variable as
> stated in the README.

> So I guess we can answer to your first question as ""where the tests
> are run from" and update the documentation. :)

Great! Thanks for clarifying :)

Note: given we most probably want to run the tests that were in the
Git repository at the very commit the ISO image was built from, either
the source tree must be shared between the build system and the
testing one, or information about the commit that was used to run the
build must be passed from the former to the latter.