Hello Neal,
Neal Gompa [2017-07-20 8:58 -0400]:
> On Thu, Jul 20, 2017 at 8:53 AM, Stef Walter <stefw(a)redhat.com> wrote:
>> As a follow up to the 'Running tests' documentation I did, I've
added
>> some documentation on adding new tests to dist-git:
>>
>>
https://fedoraproject.org/wiki/CI/Tests#Adding_tests
>>
>> Anyone up for adding some documentation for beakerlib and restraint
>> wrapping?
>>
>> Merlin, Tim, do you guys think we should add an "example" repo to
>>
upstreamfirst.fedorainfracloud.org with this example stuff in it?
>>
>
> It would be greatly helpful if there was some examples to go with the
> documentation. In part, I have been interested in the idea of having
> something "autopkgtests-ish" for snapd in Fedora. The package is
> super-complicated and I'd like to have some dedicated sanity checks
> for it whenever builds are made for it.
Not sure what you mean, but the above wiki page mostly consists of examples,
and it also links to a concrete practical gzip test
(
https://upstreamfirst.fedorainfracloud.org/gzip/c/d56637d71a8e8). That was
taken directly from the Ubuntu package's autopkgtest, i. e. the actual test
script is exactly the same. The meta-data differs between autopkgtest and
ansible, and arguably the ansible one currently contains some boilerplate[1],
but the spirit is not too different.
snapd uses autopkgtests both for distro gating and for gating upstream PRs, so
these tests should work in a Fedora context too?
I think so. I think a standard-test-autopkgtest Ansible role could be
contributed to the standard-test-roles package [0] which just uses
autopkgtest control files and staging and invocation logic directly:
This is similar to how there is a standard-test-beakerlib role and
standard-test-rhts roles.
Cheers,
Stef
Thanks,
Martin
[1] I hope that the installation and execution of the test can be done in a
generic way without having to repeat this in every individual package - but
keep in mind that this is just a PoC.