This is exactly the domain of unit testing. Curnits are basically software applications written in a mix of declarative languages. They would benefit from regular test builds and runs. Even headless would at least figure out whether the thing can load without errors. We never figured out a good solution for this. One I would suggest is a Maven project that has a unit test suite for each critical curnit and tests for important or flaky pieces of that curnit. Then putting that project into the continuous integration server will reveal errors much earlier, whenever its dependencies change.
On Fri, Oct 31, 2008 at 9:07 AM, Jim Slotta <[EMAIL PROTECTED]> wrote: > This may not be within the domain of unit testing, but is it possible > to develop tests for a curnit that look through a table of things like > this? I'm sure everyone wants to start getting away from scenarios > like this one, where jennie is urgently running tomorrow, geoff up all > night trying to figure out what's not working, COncord gets urgent > last minutes e-mails about data not saving. .. > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "SAIL-Dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/SAIL-Dev?hl=en -~----------~----~----~----~------~----~------~--~---
