Re: [Tails-dev] Automated tests specification

Delete this message

Reply to this message
Author: bertagaz
Date:  
To: The Tails public development discussion list
Subject: Re: [Tails-dev] Automated tests specification
Hi,

On Fri, Aug 28, 2015 at 04:24:51PM +0200, bertagaz wrote:
>
> I've also added a new section about the result to keep:
>
> ## What kind of result shall be kept
>
> The test suite produces different kind of artifacts: logfiles, screen
> captures for failing steps, snapshots of the test VM, and also videos of
> the running test session.
>
> Videos may be a bit too much to keep, given they slow down the test
> suite and might take quite a bit of disk space to store. If we want to
> keep them, we may want to do so only for failing test suite runs. But
> then, often the screen capture are enought to identify why a step failed
> to run. If we decide to still use them, then we probably have to wait
> for [[!tails_ticket 10001]] too be resolved.
>
> Proposal:
>
>  * For green test suite runs: keep the test logs (Jenkins natively do
>    that)
>  * For red test suite runs: keep the screen captures and the logs.

>
> The retention strategy should be the same than for the automatically
> built ISOs.
>
> I don't expect this last one to raise a lot of discussions, so let say that the
> deadline for this thread is next Sunday 12pm CEST unless some points are still
> not clear. I think the rest has already been discussed and drafted enough.


Ok, deadline has passed since almost 30 hours, so I consider the
discussion closed and I'll update the ticket accordingly.

If you forgot to send your answer, then please do ASAP. :)

bert.