Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 24 Nov 2013 17:29:33 -0500
From:      Julio Merino <julio@meroh.net>
To:        Garrett Cooper <yaneurabeya@gmail.com>
Cc:        freebsd-testing@freebsd.org
Subject:   Re: Adding new "test interfaces" to work with Kyua?
Message-ID:  <CADyfeQUaX4J1ycPhc=79P1fnfQh8E-UO349OzSL50KCJZtbOFw@mail.gmail.com>
In-Reply-To: <82E5F5E2-EA2C-46D2-9068-C419A834686C@gmail.com>
References:  <82E5F5E2-EA2C-46D2-9068-C419A834686C@gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Nov 24, 2013 at 5:09 PM, Garrett Cooper <yaneurabeya@gmail.com> wro=
te:
>         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 directio=
ns for how I can program in a new test interface so I can integrate prove t=
esting 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
there.)

But there are some details here:

https://code.google.com/p/kyua/wiki/TestersDesign

and more in the kyua-tester manual page and its references.

That said... I'm not sure now if I have detailed the "protocol" in
detail anywhere... and if not, that's something for me to start doing
:P

--=20
Julio Merino / @jmmv



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CADyfeQUaX4J1ycPhc=79P1fnfQh8E-UO349OzSL50KCJZtbOFw>