[Scons-users] HOWTO model a test suite using SCons

[William Blevins]

Stefan,

I have always used something simple like
https://bitbucket.org/scons/scons/wiki/UnitTests

I just compile my test suite and create a target for running the suite.
Obviously passing parameters to the suite via commandline is hard, but
depending on the scale of the tests, that is usually irrelevant. You can of
course make a whole pipeline using SCons targets which may include piping
the test outputs to a file and using that file as a target to a document
generator, etc.

V/R,
William

On Fri, Jan 1, 2016 at 5:37 PM, Dirk Bächle <tshortik at gmx.de> wrote:

> Stefan,
>
> On 01.01.2016 17:58, Stefan Seefeld wrote:
>
>> [...]
>>
>> In fact, I'm a little surprised that SCons' dependency graph nodes have
>> to be files. Why is that ?
>>
>
> it just *is*. At some point in the design phase it was decided to make
> SCons file-oriented and not task-oriented.
>
> Couldn't that be an abstract entity that
>> handles its notion of 'up-to-date' and 'remake' polymorphically ?
>>
>
> Possible, I'm currently planning some architectural changes which would
> make these kind of extensions a lot easier...but it'll take a while.
>
> I was
>> indeed a bit surprised reading the SCons User's Guide that all the
>> examples were based on target *files*, rather than something more generic.
>> Is there no way to define a target that doesn't involve touching or
>> generating a file ?
>>
>>
> Since version 2.4.x we have the Pseudo() target, thanks to Tom Tanner. It
> may help you...or hurt you. ;)
>
> Regards,
>
> Dirk
>
>
> _______________________________________________
> Scons-users mailing list
> Scons-users at scons.org
> https://pairlist4.pair.net/mailman/listinfo/scons-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://pairlist4.pair.net/pipermail/scons-users/attachments/20160101/e49dd222/attachment.html>