[PATCH 2/3] adt-run: add --upgrade-to option for upgrade tests

[Antonio Terceiro]

On Sat, Jun 28, 2014 at 04:49:28PM +0200, Martin Pitt wrote:
> Martin Pitt [2014-06-28 16:26 +0200]:
> > Conceptually this is still a bit weird, as the codification of what
> > the entire test is supposed to do is split between the control files
> > and test scripts (where they really belong) and command line options
> > (which might be forgotten, or specified unexpectedly, etc.). I think
> > I'd rather see a semantics where the upgrade is triggered by a flag in
> > the test control, and the command line option merely specifies the
> > target release (with a sensible default such as "current development
> > series").
> 
> This is inconsistent with what I replied to your first mail, so please
> forget the above.
> 
> So most "regular" autopkgtests should be applicable and appropriate
> after a dist-upgrade as well, so for most packages there's nothing
> needed beyond a --upgrade-to option.
> 
> For some special cases there might be tests which are only applicable
> to upgrades, and they should have a "Restrictions: upgrade" or similar
> to only run if --upgrade-to is specified; or perhaps conversely,
> "Restrictions: no-upgrade" for tests which are known to not work in
> the next distro series (although this is weird, and I'd rather avoid
> it; the test can still exit early if it detects an incompatible
> release).

In the case I was testing I would need to be able to specify that a set
of tests only applies to the specific case of a wheezy→jessie upgrade,
but as you said, maybe those tests could just exit early if that is not
the case?

-- 
Antonio Terceiro <terceiro at debian.org>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/autopkgtest-devel/attachments/20140628/d8c92574/attachment.sig>