X-Authentication-Warning:	delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient:	geda-user AT delorie DOT com
X-Original-DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=gmail.com; s=20120113;
	h=mime-version:from:date:message-id:subject:to;
	bh=jO/gitWnQ9kKd2kyW8xyI/cnV7H1Q+++bzD3E3RsKdo=;
	b=VouWVr2V64GzqLtj5lE/7S+nEI/bHetTiXXsZm15lpi4QRlSP6/luME39MV5oFUkKG
	1l05CvlCxkvfBq0oHqJrRLoB0gIx362m/fus2YttySaHMC64wSwkrPLoBfCVQS4N75sQ
	Js6DOu1n/RDleKV71FMkAqQuMpuTxD0pyepO5C32qQdiA5ypPLAh28IUc02ahuyIZ7Uq
	jXC8U68R6zXwCRYz1R2uxDwdwxyS6jIehEgI9Th3++GKG/VmQaqBEKbOGxa03Y7UPrhO
	1ghSqQ+HjuUY1/kKbEfHXY2AKUIt/nEtj6mr8rQWaPNu9FrrKqR7Jmc8dBsoXfv3XwOG
	VyGQ==
X-Google-DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20130820;
	h=x-gm-message-state:mime-version:from:date:message-id:subject:to;
	bh=jO/gitWnQ9kKd2kyW8xyI/cnV7H1Q+++bzD3E3RsKdo=;
	b=EegogQv2un3hBPVp/vJx6ibSguqfUwCb32uAZADPjCXVL5X6uszxbXgU3Bin8UOZKn
	BNB7TPuqdiLOESxJJIVqenovx0vRl+hQVcF4m4MMQLl7eKlT/fPpAPeCMTlWa0QjKLAM
	YZz+GFo6+QHnOPnyhrZGwSCbBJdP5ClPSbMXR49M/X+A0ZBfNCWsazMgj25UP+AwGu0b
	ZaAlvo7ApKoVGkdYOajRI+BkYL9I1ZgHGre6wMQnmsKQ4fRp+UhMeKmdrT0ERMcTvGuG
	xCbpjKuiAIZHNKpqNMMMFKbLGZ8Pk+5KSu0IHUMDbPz4cTvKnVq1Zt+OWqdBv+eo+TxO
	zAZw==
X-Gm-Message-State:	AEkoouvW4+YgCbXLRb0e7o7UCtVMCuvQD/KvEdsFNnEZe8jSE6zsERKlcz7PLF3ota4i2t5DMNvRAGEag0QxJg==
X-Received:	by 10.28.9.194 with SMTP id 185mr17365573wmj.37.1470700700760;
	Mon, 08 Aug 2016 16:58:20 -0700 (PDT)
MIME-Version:	1.0
From:	"Britton Kerin (britton DOT kerin AT gmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
Date:	Mon, 8 Aug 2016 15:58:20 -0800
Message-ID:	<CAC4O8c81kb=9Tei2judPeYJKiq51WpZ154JVuakqW=0RXx6bCQ@mail.gmail.com>
Subject:	[geda-user] upgrading the testing framework for pcb, please object now
To:	geda-user AT delorie DOT com
Reply-To:	geda-user AT delorie DOT com

So not having heard back on the question of how we wanted to do tests,
I decided it would be better to go with glib-based g_test_* testing,
instead of the end-to-end tests in the tests subdir.  The main reason
is that this will make it possible to directly test interfaces that
aren't exposed as actions.

Currently only pcb-printf uses this approach, and since it's a
stand-alone interface it (correctly) doesn't create a full pcb context
for it's tests to run in.  However, many other tests require more
context.
Therefore what I intend to do is:

* leave the existing unittest about as it is.  All tests of
stand-alone modules in pcb can go there

* make a new main-contex_tests.c or something that provides everything
you would find in a running pcb instance except the gui stuff.  I've
already got this working it just needs split off from the existing
unittest and some cleanup.

If this isn't ok please let me know now.

Britton

- Raw text -