[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: run BISTs for all installed packages

From: Andrew Janke
Subject: Re: run BISTs for all installed packages
Date: Tue, 5 Mar 2019 10:59:01 -0500
User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:60.0) Gecko/20100101 Thunderbird/60.5.1

On 2/7/19 2:41 PM, Andrew Janke wrote:

On 2/5/19 11:41 AM, Mike Miller wrote:
On Tue, Feb 05, 2019 at 11:09:43 -0500, Andrew Janke wrote:
In core Octave, are those the tests that end up in
matlabroot()/share/octave/4.4.1/etc/tests ans *.cc-tst or in the Octave
source tree as *.in.yy-tst files? Maybe we could add a mechanism to packages
to similarly extract them to *-tst files?

Yes: https://savannah.gnu.org/bugs/?41298

It looks like you are interested in helping to improve and expand the
features of Octave's test suite functions, which is great. Please do
have a look at prior bug reports, discussions, ideas, and prior art
because there is a lot of it out there.

There have been discussions on a lot of this already, including a "pkg
test" subfunction, installing "-tst" files for compiled code in pkgs,
refactoring and deduplicating code between "runtests" and

You might also want to look at the Debian dh-octave package, which
implements its own method for running all tests in a source package at
build time and in a CI environment.

Thanks; I hadn't seen that bug and wasn't aware of the dh-octave package. I'll have another pass through the issue tracker to make sure I'm up to date.


I've put together a list of references to bugs and Octave maintainers mailing list threads related to enhancing the test suite: https://github.com/apjanke/octave-testify/blob/e6e9cd4117c6d6e601a8c00487dc75769aa1699f/doc-project/Developer-Notes.md

Any major ones I'm missing?


reply via email to

[Prev in Thread] Current Thread [Next in Thread]