Manish Sapariya wrote:
I ran into same problem and it worked. I had one question though? setup
and teardown is
called for every test in given test class. I don't understand the
reasoning behind this usage
model.
setup and teardown are methods Watir scripters sometimes choose to
import from Test::Unit, which is a unit testing framework. It is very
standard in unit testing to not have your unit tests change the state of
the application under test. Many people value being able to run any
subset of their unit tests in any order, without having to worry that
the order might effect the results.
The second thing, if I want to run more than one test case after
setting the system
in particular state, how can I achieve that?
Happily, setup and teardown are also optional methods for those of us
using Watir. If you don't want something to happen automatically at the
beginning of every run, don't put it in setup. Likewise with teardown.
For functional automation I often don't include these methods at all.
Cheers,
Jeff
_______________________________________________
Wtr-general mailing list
Wtr-general@rubyforge.org
http://rubyforge.org/mailman/listinfo/wtr-general
