On Sun, Nov 28, 2021 at 11:14:19PM -0500, Sandro Tosi wrote: > Package: autopkgtest > Version: 5.16 > Severity: normal > X-Debbugs-Cc: [email protected] > > Hello, > while adding autopkgtests to a package, it seems the only way to iterate over > them (adding new tests, fix broken ones) is to fix them in the source package > and rebuild it. > > There are packages that takes hours to build, and that's essentially to write > a handful of files in the source package. > > Is there a better way to incrementally work on autopkgtests that doesnt > require > to waste hours (sometimes days) just waiting for the source package to build? > > I think that would greatly improve the developers experience.
This has always been possible. You can run the tests directly from the source tree, using previously built .debs: autopkgtest --no-built-binaries ../*.deb . -- [...] The above works for any virtualization backend. If you already have the right binaries installed on your host system and want to run the tests without any virtualization, it's even simpler: autopkgtest -B . -- null I have the above aliased as `a`. (-B is the short form for --no-built-binaries). We should probably add an examples section to the manpage with this type of invocations.
signature.asc
Description: PGP signature
