Oops, I think I left one thing unclear in this proposal:
- each library would have a 'unittests' folder for the tests that are specific to that library. Ideally each object would have a test patch in the 'unittests' subfolder in the library, but we're a ways off of that.
.hc
On Nov 3, 2011, at 10:27 AM, Hans-Christoph Steiner wrote:
So now that Katja has a nice testing patch and has written a bunch of tests, I think we need to nail down a standard naming and location for the tests. I think that 'unittest' should be the standard name for them. Then the patches will be called 'osc~-unittest.pd', the library subfolder will be called 'unittests', and then I think we need a new section in trunk called 'unittests'.
This 'unittests' section will be for unit test patches that are not specific to a single library, but test interactions between objects from different libraries. It could also be the place where all of the testing frameworks go, like the scripts that automate the running of the tests, the *-unittest.pd templates, etc.
How does that sound?
.hc
----------------------------------------------------------------------------
Mistrust authority - promote decentralization. - the hacker ethic