Adding new "test interfaces" to work with Kyua?
julio at meroh.net
Mon Nov 25 17:21:02 UTC 2013
On Sun, Nov 24, 2013 at 5:34 PM, Garrett Cooper <yaneurabeya at gmail.com> wrote:
> On Nov 24, 2013, at 2:29 PM, Julio Merino <julio at meroh.net> wrote:
>> On Sun, Nov 24, 2013 at 5:09 PM, Garrett Cooper <yaneurabeya at gmail.com> wrote:
>>> Trying to reconcile my diffs and get things sane again, I realize that due to refactoring (and especially after I installed devel/kyua) that prove.test.mk no longer functions for me off my branch. Are there directions for how I can program in a new test interface so I can integrate prove testing into Kyua?
>> What kind of interface do prove-based test programs have? Are they
>> binaries/scripts that you can just run and assume that a 0 exit code
>> means passed and 1 means failed? If yes, you'd just funnel them
>> through the 'plain' interface and they should just work as a first
>> cut. (I believe this approach works for most test programs out
>> But there are some details here:
>> and more in the kyua-tester manual page and its references.
> It’s a bit more complex than that. nose and prove both implement collection and execution test features, meaning that it goes and figures out what to execute (for nose it’s a variety of parameters — filename, mode, etc — that determine whether or not it’s testable; for prove it’s all files with a .t extension), then executes it.
Bleh. Turns out that prove-based test programs do not return 1 on
failure. Time to write a prove tester given that I have some spare
time this week :-P
Julio Merino / @jmmv
More information about the freebsd-testing