Forum Discussion
Thomas_Fuller
16 years agoOccasional Contributor
I've uninstalled SoapUI 3.5 on my machine and installed 3.5.1. Strangely enough 3.5.1 reveals a different problem than 3.5.
3.5: -- for tests that fail the problem returned from the server is a hibernate exception. This is working on another machine using the same version of Soap UI. Maybe my installation was botched up or something but I uninstalled and then reinstalled the SoapUI 3.5 software and the results are the same (ie. still failing).
3.5.1 -- for tests that fail the problem is that the user is not authenicated.
Now this puts me in exactly the same position as my colleage: he has 3.5.1 on a brand new Dell laptop, same tests, same code, and authentication fails for him when he runs the test suite.
However if, instead of running an "Run[authenticate] TestCase" he clones the actual authenticate Soap test step into the failing test case, everything works as expected (ie. the tests pass).
The investigation continues...
Tom
3.5: -- for tests that fail the problem returned from the server is a hibernate exception. This is working on another machine using the same version of Soap UI. Maybe my installation was botched up or something but I uninstalled and then reinstalled the SoapUI 3.5 software and the results are the same (ie. still failing).
3.5.1 -- for tests that fail the problem is that the user is not authenicated.
Now this puts me in exactly the same position as my colleage: he has 3.5.1 on a brand new Dell laptop, same tests, same code, and authentication fails for him when he runs the test suite.
However if, instead of running an "Run[authenticate] TestCase" he clones the actual authenticate Soap test step into the failing test case, everything works as expected (ie. the tests pass).
The investigation continues...
Tom