Missing atf-check output: example:failing_test -> failed: atf-check failed; see the output of the test for details

[Fabian Keil]

Alan Somers <asomers at freebsd.org> wrote:

> On Fri, Jul 25, 2014 at 12:55 PM, Fabian Keil
> <freebsd-listen at fabiankeil.de> wrote:
> > I'm currently evaluating using kyua to test a FreeBSD-specific
> > shell script, however I'm having trouble analysing failing tests.
[...]
> > I get:
> >
> > | fk at r500 ~/git/zogftw/tests $kyua --loglevel debug test -k Kyuafile example:failing_test
> > | example:failing_test  ->  failed: atf-check failed; see the output of the test for details  [0.150s]
> > |
> > | 0/1 passed (1 failed)
> > | Committed action 21
> >
> > The test failure obviously is expected, but I'm missing the referenced
> > "output of the test". The relevant log excerpt:
[...]
> > I'm looking for something like this:
> >
> > | fk at r500 ~ $/usr/local/libexec/atf-check -s exit:1 -o empty -e empty 'true'
> > | Executing command [ true ]
> > | Fail: incorrect exit status: 0, expected: 1
> > | stdout:
> > |
> > | stderr:
> > |
> >
> > I didn't read all the docs available yet and I may be missing something,
> > but seeing test failures is something I'd expect to work out of the box.
> > Can someone familiar with kyua confirm that this is working as expected?

> The test output is stored in Kyua's sqlite database.  There are two
> ways to see it:
> 1) Run " kyua report-html"
> 2) Sometimes its easier just to rerun the testcase in debug mode.  Do
> "kyua debug example:failing_test"

Thanks a lot.

Not showing test failures on the cli by default seems like a strange
design decision to me, but I guess I'll get used to it or write a
wrapper script that calls kyua debug for all tests.

Fabian
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-testing/attachments/20140726/f4615ca8/attachment.sig>