On Tue, 4 Oct 2016 20:09:14 +0100
"Richard W.M. Jones" <rjones(a)redhat.com> wrote:
On Mon, Oct 03, 2016 at 08:21:42PM +0000, Zbigniew
Jędrzejewski-Szmek
wrote:
> On Mon, Oct 03, 2016 at 01:50:33PM -0600, Tim Flink wrote:
> > One of the features for Taskotron that we've been planning since
> > the beginning was a way for contributors to maintain their own
> > automated tasks/tests which would be run during a package's
> > lifecycle.
> >
> > I'm happy to say that we're almost to this milestone and wanted
> > to get some feedback from devel@ on the specifics of what we're
> > planning WRT where these automated tasks will be stored and the
> > execution modes that we're planning to support. Our current plan
> > is written up at:
> >
> >
https://phab.qadevel.cloud.fedoraproject.org/w/taskotron/new_distgit_task...
>
> Sounds reasonable.
>
> How does the environment in which those tasks are run look?
> Would it be possible for example to run a test which launches
> a qemu VM to test stuff that requires a functional installation
> and a reboot?
And related to this question, do we also need to define
"TestRequires" packages/dependencies?
There are 2 ways of installing dependencies for task execution:
1. List the dependencies in the formula so that they're installed
during setup
2. Install them with a script that runs as part of the task - you have
root access on the VM and can do whatever you need to for testing,
even rendering the machine non-bootable because the next task will
get a fresh VM created from a base image.
Does this answer your question or did I misunderstand what you were
asking?
Tim