On Oct 20, 2006, at 7:29 PM, Ian Wood wrote:
On 21 Oct 2006, at 03:15, kee nethery wrote:
On Oct 20, 2006, at 12:46 PM, Andre Garzia wrote:
One thing we trylu need is a Suite of Tests that test a rev
distribution for obvious bugs. This little stack could be
executed and it would test things. Many languages have this kind
of suite, Ruby has it and so does scheme. This would help finding
bugs in new releases.
How about one master stack that looks in a folder, lists all the
stacks in that folder, then sends each one a command to execute
it's tests, and accepts a callback when the test is done. Then
each of us could create test stacks to test a function and send
them to runrev and they could run them as unit tests. If we did
this for each bug that got submitted it might help them QA new
versions.
Rather than callbacks, I'd probably go for things being called from
the openstack handler with results being written to a text file
with the same name as the test stack. That way you just launch each
stack and don't have to worry too much about communication.
Good idea.
At WWDC the Apple Safari team indicated they use the slowest Mac that
have to run all their regression tests, makes it easier to compare
differences in timing.
Kee
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
