On 30 Apr 2015, at 16:35, Peter W A Wood <[email protected]> wrote: > > I have written a few automated test scripts to test elements of LiveCode. The > testing commands and the tests were all in a single script. I’m now about to > modernise a stack I use personally and want to develop a set of tests for it > as I write it. > > Rather than copy and paste the few testing commands into another script, I’ve > pulled them together into a very simple toolkit for testing LiveCode stacks > and scripts. I call in Mini Test. I thought it may be of some use to others > so I’ve written some very basic documentation and published it on Github. It > can be found at https://github.com/PeterWAWood/LiveCode-MiniTest > <https://github.com/PeterWAWood/LiveCode-MiniTest> > > Regards > > Peter
As examples of using LiveCode MiniTest, I’ve converted to Mini Test a few tests of LiveCode that I have written in the past to test features of LiveCode. I’ve published these tests on Github at https://github.com/PeterWAWood/LiveCode-Tests <https://github.com/PeterWAWood/LiveCode-Tests> There is an example of a stack to run the tests in the IDE and another to run the tests with LiveCode Server. There are three test files which are run by both test runners, happily with identical results. Regards Peter _______________________________________________ use-livecode mailing list [email protected] Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
