Funny you should mention the subject. I'm sorry but I've been very busy lately and haven't finished the work on handling failure in test setups. When I stopped work 2 weeks ago, I was still thinking about how to
handle a null test contacts list...
... however, I also had a note to myself to look into how tests fail when the system is not connected to the internet in various ways. I had been thinking I would catch the Exception(s) in the start() methods of the slicks
and then install a special jUnit test that will fail with a meaningful message.
In other words, don't have a special property to stop the tests running - let the tests that depend on the internet fail gracefully when they can't find what they need.
I won't have time to work on the project until next week (at the earliest), but I didn't want you to go ahead without knowing my thoughts.
On Wed, 26 Jul 2006 16:18:22 +0200, Emil Ivov wrote:
I had problems with my internet connection lately and was obliged to
comment numerous parts of the tests (icq slick) in order to be able to
continue my work without connectivity.
I was thinking of adding a DISABLE_ONLINE_TESTING property
(default=false) to the test conf files. When set to true tests that
require an internet connection won't be registered. The same goes for
any other method call requiring network connectivity (such as tester
agent account setup in icq for example).
The downside is that there's no automatic global way of doing it and
that it would be up to test implementors to respect this so we may
encounter incoherences later on.
The other thing is that this may lead to situations where many of us
won't run the online tests at all (since it generally takes longer to
complete) and would be tempted to commit without doing it ... this is
less serious though since we have CC which would help us rapidly
discover the case.
Any other opinions on this issue?
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com