Hi Dmitry,
Max, you asked me to add some customization in unit tests.
I don't recall that. I recall I said that we should not hardcode possible connection
information in the unittests at least not without it being customizable so anyone can set
it up and run it.
All customization variables hold in Customization class as filds.
I'm not sure what you are asking me about ?
Which test is this (package/classname?) ?
/max
As you know we have scope of unit tests which run for each package.
This
means each unit test runs so much times as the number of packages we have.
So we have option of changing view:
1.1) detailed view - we see each test run (I painted here horisontal
lines to easier understanding.)
I haven't idea how report which package was tested when we haven't errors.
But when we have - I say it in fail message.
1.2) Compact view - each test as one.
2) Statistics switch
3) test packages with name pattern (use if do not want to test all 111
packages)
4) stop testing after the first fail/error switch
5) delays between each pack testing - use if you want make some actions
by hand, and before tearDown.
This is all I've devised so far.
Max, do you have any other requests, propositions?
--
Using Opera's revolutionary e-mail client:
http://www.opera.com/mail/