From owner-freebsd-testing@FreeBSD.ORG Mon Apr 13 20:45:40 2015 Return-Path: Delivered-To: freebsd-testing@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 8E9E3566 for ; Mon, 13 Apr 2015 20:45:40 +0000 (UTC) Received: from mail-vn0-f53.google.com (mail-vn0-f53.google.com [209.85.216.53]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4363E630 for ; Mon, 13 Apr 2015 20:45:39 +0000 (UTC) Received: by vnbf129 with SMTP id f129so23719130vnb.9 for ; Mon, 13 Apr 2015 13:45:33 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=P1Lp5S5y1jr5VEh7CqCYtFa73b2vw8Q1yWaB4rHXWdY=; b=BIycSU8yawMX8NNpSoM4vl2Bh1xmTWQk3Std88lI5wsnmExPHWGi2kDacDVDrtepVG H5W9I97CZ9ns3b8h+IynpGMe8GHyXEdTXaD5k0cBavHLQcsAoHufe7EXQwwnFk1k4KLa cMdIb1Pg4MpR/1CuZoZ/rCKwstsvRuwGggoiUZSjbaxSM6n3Z8iBP5AIBGq4XoALcgmG sxxHdaN2gF7FfIY0/+qP+nL0SnATTQWykPY3HsHlY4IwsHGPPVHO9eJ+WUcBgunKrT7J QFErbE/Lk6DJ29xT8YJ0glf46/sRQy4jt86zipCntHDGvZKMQz7FB9oRweUeYh8kRMGj uuJg== X-Gm-Message-State: ALoCoQmeboL2x8re09DdUkyUZIlQaACKTL7HiPl9OuPHduPHUyDg/+RW4GNFrGxjzBFXvXOhgLmE X-Received: by 10.236.104.167 with SMTP id i27mr13763291yhg.62.1428957933017; Mon, 13 Apr 2015 13:45:33 -0700 (PDT) Received: from ?IPv6:2620::1003:1007:bcb8:a1f8:f77:e3a7? ([2620:0:1003:1007:bcb8:a1f8:f77:e3a7]) by mx.google.com with ESMTPSA id g46sm7812749yhd.42.2015.04.13.13.45.32 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 13 Apr 2015 13:45:32 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) Subject: Re: Python unittest backend for Kyua From: Julio Merino In-Reply-To: Date: Mon, 13 Apr 2015 16:45:31 -0400 Content-Transfer-Encoding: quoted-printable Message-Id: References: <20150214215750.GA5065@rodrigc-laptop1> To: Alan Somers X-Mailer: Apple Mail (2.2070.6) Cc: "freebsd-testing@freebsd.org" X-BeenThere: freebsd-testing@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Testing on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Apr 2015 20:45:40 -0000 [Here I am apologizing for delays again... that's it, I'm re-enabling = email notifications for my OSS email account; splitting it off didn't = work as intended.] On Mar 2, 2015, at 19:07, Alan Somers wrote: > Well, maybe I should dust off my old branch and get back to work. But > I don't know how my python tester would work with your executor > branch. If I understand correctly, the executor branch dispenses with > the *-tester binaries and calls the test programs directly from the > kyua executable, correct? The python tester relied on the tester > being a separate binary. The tester was actually implemented in > Python, which made it very easy for the tester to interact with > individual test cases. How would I accomplish that on the executor > branch? I think your approach of writing the tester in Python was a good one, as = that allows the introspection features you mention. To plug it into the executor code, we'd need to explicitly write a new = backend type that invokes external programs. I have not thought much = about it, but it's possible to make this as generic as the previous code = was. Or maybe we shouldn't make it generic, and instead we should just = have a native pyUnit primitive. If you have interest in moving this forward, we can discuss. But the = executor code is about to receive some other big changes to properly fix = one regression that was introduced, so I'd wait a little bit longer. Cheers=