Re: Running the test suite independently of the build
"Todd C. Miller via sudo-workers" <[email protected]> Fri, 15 May 2026 08:24:24 -0600
| Newsgroups | gmane.comp.tools.sudo.devel |
|---|---|
| Message-ID | <[email protected]> |
On Fri, 15 May 2026 14:09:10 +0200, Marc Haber wrote: > make check runs the test suite after a successful build. And even right > after a successful "make", it still compiles things before doing > testing. Make installcheck doesn't work at that stage. The test binaries for things like unit tests (as well as testsudoers) are not build by default. > Does make installcheck depend on actually having done make install > before? Sudo doesn't currently support an installcheck target. > Debian's autopkgtests work by building the actual package, installing it > the normal way like an end user would, and then running the tests > against the installed package, calling /usr/bin/sudo etc. autopkgtest > can run without having the package built before, and it even _usually_ > runs from a source tree that was not build before (since our tooling > makes a copy of the source tree and builds there). Many (most?) of the tests are not testing the installed binaries. There is a combination of tests for specific functions as well as tests for behavior using "testsudoers". The only tests that could run against the installed version of sudo would be the ones that use visudo. How does Debian normally deal with packages that include unit tests? - todd ____________________________________________________________ sudo-workers mailing list <[email protected]> For list information, options, or to unsubscribe, visit: https://www.sudo.ws/mailman/listinfo/sudo-workers