Re: Format of test specifications

[Felix Lechner <felix.lechner@lease-up.com>]

Hi,

On Fri, Dec 7, 2018 at 1:24 PM Chris Lamb <lamby@debian.org> wrote:
>
> > The format for test specifications in 'desc' mixes template fill data
> > (Package-Architecture:) with test options (Output-Format:) and
> > constraints (Test-Architectures:). I would like to split it into three
> > files.

I have an incremental build system for the test packages. It requires
build specifications separately from the evaluation parameters. Unless
there are objections, I will convert the test suite in the near
future.

The layout for each test case will look something like this:

In t/tags/checks/debian/symbols/package-placeholder:

    ./build-spec/fill-values
    ./build-spec/debian/package-placeholder.symbols
    ./eval/desc
    ./eval/tags

> Could you elaborate more why?

When evaluation parameters are part of a build specification, they can
cause unnecessary rebuilds. Editing a check, for example, can result
in new expected tags (like removing the quotes in field-too-long) but
should never trigger the rebuilding of test packages.

In general, it will make testing faster everywhere and also provide
fewer excuses for commits failing on Gitlab. :)

Kind regards,
Felix Lechner