From owner-freebsd-testing@FreeBSD.ORG Mon Nov 25 02:01:54 2013 Return-Path: Delivered-To: freebsd-testing@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6995C608 for ; Mon, 25 Nov 2013 02:01:54 +0000 (UTC) Received: from mail-la0-f51.google.com (mail-la0-f51.google.com [209.85.215.51]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id E847D2307 for ; Mon, 25 Nov 2013 02:01:53 +0000 (UTC) Received: by mail-la0-f51.google.com with SMTP id ec20so2541124lab.10 for ; Sun, 24 Nov 2013 18:01:46 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type:content-transfer-encoding; bh=Cvr4WZqLQqG9KsGqIhpVHVEKPm7AviRBajFkrgzZl0I=; b=QjVeLXfABT3nTBUsRj2ypf6qRicCGSqmCjpNTzygv2RcHkNo6ZZDpjaFhh7HjgS9+b BMSf1u4E1LFgcOwcPUvmKdqCOoSe+DP4DDif4hBUupHbI3ZahNPTNFXPdMkvz1TnA/d7 Djso6y0oricw+4dI23epvQNTZv04Cz6bzEwklfIy6KaXwE5xhBgGb1nPB4xesL/7rHKe aZDEchHaseIERB3gnyhkgfTJ1aqKsxgQCh2iD63Phmuy74rU5+5mI9+N8y2z52guYQBZ RUucEdQo5zES5MqtcgKLxY/BT3s9iIBmt2547JjBiYhJCbaTO6SgS03xQ+L5mU/zgosu z9Nw== X-Gm-Message-State: ALoCoQlKMInHXXsBm6MXrPKYzOhLicHyD38T4s79t/kYyC8KabOVYrN7Zatshr8Xt8AOySRY3tNE X-Received: by 10.112.172.137 with SMTP id bc9mr19671289lbc.21.1385344510906; Sun, 24 Nov 2013 17:55:10 -0800 (PST) MIME-Version: 1.0 Received: by 10.112.168.65 with HTTP; Sun, 24 Nov 2013 17:54:50 -0800 (PST) X-Originating-IP: [108.176.158.82] In-Reply-To: <751B8D9F-9A1B-46B5-80F8-CB9E44F98BFC@gmail.com> References: <82E5F5E2-EA2C-46D2-9068-C419A834686C@gmail.com> <751B8D9F-9A1B-46B5-80F8-CB9E44F98BFC@gmail.com> From: Julio Merino Date: Sun, 24 Nov 2013 20:54:50 -0500 Message-ID: Subject: Re: Adding new "test interfaces" to work with Kyua? To: Garrett Cooper Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Cc: freebsd-testing@freebsd.org X-BeenThere: freebsd-testing@freebsd.org X-Mailman-Version: 2.1.16 Precedence: list List-Id: Testing on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Nov 2013 02:01:54 -0000 On Sun, Nov 24, 2013 at 5:34 PM, Garrett Cooper wro= te: > On Nov 24, 2013, at 2:29 PM, Julio Merino wrote: > >> On Sun, Nov 24, 2013 at 5:09 PM, Garrett Cooper = wrote: >>> Trying to reconcile my diffs and get things sane again, I realiz= e that due to refactoring (and especially after I installed devel/kyua) tha= t prove.test.mk no longer functions for me off my branch. Are there directi= ons 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 >> 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. > > It=92s a bit more complex than that. nose and prove both implement collec= tion and execution test features, meaning that it goes and figures out what= to execute (for nose it=92s a variety of parameters =97 filename, mode, et= c =97 that determine whether or not it=92s testable; for prove it=92s all f= iles with a .t extension), then executes it. I need to read about that a bit more then. Is there a web site for these tools? Their names are so generic that it's hard to find stuff. That said, I have started to take a look at the existing .t tests... and the majority of them seem to be just wrappers that execute a shell script. In these cases, I think we should just drop the .t and use the plain interface to execute the existing shell script. By pure coincidence, I had been working today on "porting" a couple of these tests; expect a patch for the proof of concept soon. > I=92d like to take the error messages and make them more meaningful thoug= h, because it doesn=92t help if something fails and I need to diagnose why = it failed, but lost the info I need to debug the problem... As long as these print the error messages to either stdout or stderr, they will be captured by Kyua and stored into the reports. --=20 Julio Merino / @jmmv