Hi!
We've already voted for this issue.
The problem is that when such an exception comes up during a test, it's fine
that the test fails, but any test that is executed after the one failed test
should be unaffected by a failure of an earlier test.
When an application is run normally we can live with ULC terminating the
application on such an occasion. The application is in an undefined state
then. Some bug has surfaced and should be fixed. In a test we try to find
bugs. So when one bug kills the whole test suite, we don't now what effect
it really has. Are all test scenarios affected or is it only the first
failed one?
So for this case keeping the session alive and also having the possibility
to reset it would be very helpful.
Cheers,
Robert
----- Original Message -----
From: "Daniel Grob" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Wednesday, September 27, 2006 3:32 PM
Subject: Re: [ULC-developer] Problems with Jemmy-Testing
Hi Robert,
At the moment UBA-943 is not scheduled to be fixed in the next release.
However, the number of votes for a JIRA issue has an effect on release
planning. Therefore please vote for UBA-943.
Until now we were a little bit reluctant to fix this issue because an
exception means that something has gone wrong and the application (or ULC)
might be in an inconsistent state. And continue the operation on an
inconsistent state might lead to loss of data or other harmful things.
For the current ULC release I cannot see a way to continue an ULC
application that has issued an uncaught exception. Sorry.
Griessli Dany
Hi!
We are using the code from the code community for testing with Jemmy (
http://ulc-community.canoo.com/snipsnap/space/Contributions/Integration+Snippets/UI+Testing+with+Jemmy )
. It works fine. The only problem is that when an uncaught exception
occures, the session is closed and all further tests fail because they
are working with a closed session. I tried to fix this by restarting the
DevelopmentRunner, but it's all to no avail. It won't work - no matter
how I try.
Now I found this ( https://www.canoo.com/jira/browse/UBA-943 ). I think
that it would hellp greatly. I could fetch the exception and let the
current test fail with it, but the session would stay alive and could run
the following tests. Is there some estimation when this might be fixed.
Any other idea how to get rid of this testing problem is also welcome.
Cheers and thanks in advance,
Robert
_______________________________________________
ULC-developer mailing list
[email protected]
http://lists.canoo.com/mailman/listinfo/ulc-developer
_______________________________________________
ULC-developer mailing list
[email protected]
http://lists.canoo.com/mailman/listinfo/ulc-developer
