This is one section I would like to have in the announcement for developers because this allows for test encapsulation.
On Tue, Sep 29, 2015 at 6:57 PM, William Blevins <wblevins...@gmail.com> wrote: > I added the functionality for (1) in the CL-patch since I wanted to look > for contents without haven't to include stdout of unrelated information. > > V/R, > William > > On Tue, Sep 29, 2015 at 6:10 PM, Gary Oberbrunner <ga...@oberbrunner.com> > wrote: > >> >> On Tue, Sep 29, 2015 at 12:08 PM, Bill Deegan <b...@baddogconsulting.com> >> wrote: >> >>> Gary, >>> >>> For this test I ended up just having the full expected output, in this >>> case I effectively checked for the output not being there. >>> It worked for the negative case because the output is pretty short. >>> >>> Can you use must_not_contain on stdout? >>> I'm thinking our test framework docs are pretty sparse. >>> >> >> There's a _small_ amount in the wiki, at >> https://bitbucket.org/scons/scons/wiki/DeveloperGuide/TestingMethodology/QMTestMethods >> and >> https://bitbucket.org/scons/scons/wiki/DeveloperGuide/TestingMethodology. >> The README in the QMTest dir is not all that helpful; that'd be a good >> place for some of this IMHO. >> >> >> -- >> Gary >> >> _______________________________________________ >> Scons-dev mailing list >> Scons-dev@scons.org >> https://pairlist2.pair.net/mailman/listinfo/scons-dev >> >> >
_______________________________________________ Scons-dev mailing list Scons-dev@scons.org https://pairlist2.pair.net/mailman/listinfo/scons-dev
