ATF-log archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: #55: Make atf-run resilent to missing test programs
- Subject: Re: #55: Make atf-run resilent to missing test programs
- From: "atf trac notification" <nobody%julipedia.org@localhost>
- Date: Sun, 01 Aug 2010 06:51:18 -0000
#55: Make atf-run resilent to missing test programs
-----------------------+----------------------------------------------------
Reporter: jmmv | Owner: jmmv
Type: defect | Status: accepted
Priority: critical | Milestone: 0.11
Component: atf-run | Version:
Resolution: | Keywords:
-----------------------+----------------------------------------------------
Changes (by jmmv):
* cc: gcooper@... (added)
Comment:
What do you mean? atf-run currently detects test programs that are
"broken": i.e. test programs that not conform to what atf-run expects.
For example, if a test program fails to create the results file, it is
considered broken. It'd be pretty easy to report missing test programs in
the same way.
In my opinion, an Atffile that points to a missing test program should be
reported as an error in the Atffile itself (which is what atf-run does
nowadays in a pretty drastic way). Pretty much like make(1) does when it
encounters a missing source file. But this has turned out to be suboptimal
because the smallest typo in an Atffile results in the whole test suite
not running...
Alternatively, we'd just make atf-run be more verbose regarding the
"missing test program" error and live with it, because the current error
message is too cryptic.
--
Ticket URL: <http://www.julipedia.org/projects/atf/trac/ticket/55#comment:3>
Automated Testing Framework <http://www.NetBSD.org/~jmmv/atf/>
Automated Testing Framework
Home |
Main Index |
Thread Index |
Old Index