Raghu Venkataramana wrote: > >> * What do you mean by "Test run in batch mode consistently". You said >> that WET does this but Watir doesn't. This sounds like something pretty >> important that Watir should be doing. What did you do to fix this in WET? >> > A combination of two things - > a) Test definitions to describe a test completely. The test > definitions include preconditions > and teardowns which ensure that a test's dependencies can be called > before the test itself. > > b) BatchRunner to define the order in which tests are executed - > > Without these we found that tests were being run in an alphabetical > order rather than the order > in which tests were defined. Many a time, execution of a test depends > on the fact that previous tests > have been run and this was causing tests to break when run in a batch > mode. That's when we invented > the 'preconditions / teardowns' support + the batch mode of execution Thanks for the clarification. I agree that WET is providing a feature that Watir doesn't have. Strictly speaking Watir has been only a GUI Driver, and what you are criticizing is Test::Unit, but that in fact is the test harness that comes bundled with Ruby and which we have encouraged users to use. As you note, there are problems with using it for System testing, since it was designed for unit testing.
I guess i would label this feature "System Testing Test Harness". Of course, I recently bundled Watir::TestCase. This solves part of the alphabeticization problem. These tests will run their test methods in the order defined, rather than alphabetically. Bret _______________________________________________ Wtr-general mailing list [email protected] http://rubyforge.org/mailman/listinfo/wtr-general
