Re: Testing cleaning

Russel Winder <[email protected]> Wed, 19 Apr 2017 04:03:09 +0100

Newsgroups	gmane.comp.programming.tools.scons.devel
Message-ID	<[email protected]>

On Tue, 2017-04-18 at 17:05 +0000, Managan, Rob wrote:
> Russel,
> testing/TEX/clean.py has one example of running the build with the “-
> c” option and then checking that certain files don’t exist

I added such a call (thanks also to Bill for similar suggestion) and
tests for non-existence of files after the build and test for existence
of files, and it all seems to work. Which is great. I now realise this
should have been added to all the other D tests. A canonical end-to-end 
test of this sort should be:

1. Build project.
2. Test expected files are there; try and test for no unexpected files.
3. Run application and test reasonableness, or build against newly
created library.
4. Clean project and ensure all created files are removed.

Once this pull request passes review and is merged, I shall update all
the other D tests along these lines.

-- 
Russel.
=============================================================================
Dr Russel Winder      t: +44 20 7585 2200   voip: sip:[email protected]
41 Buckmaster Road    m: +44 7770 465 077   xmpp: [email protected]
London SW11 1EN, UK   w: www.russel.org.uk  skype: russel_winder

_______________________________________________
Scons-dev mailing list
[email protected]
https://pairlist2.pair.net/mailman/listinfo/scons-dev

signature.asc (application/pgp-signature, 833 B)