Forum Discussion

Thomas_Fuller's avatar
Thomas_Fuller
Occasional Contributor
16 years ago

Strange behaviour with Soap UI Pro on different machines

Hi,

We have a test suite that runs with (currently) a few tests breaking on my machine (running Windows XP + SoapUI Pro).

A colleague of mine has Soap UI Pro on a machine running Windows 7.

It is important to note that the code our application is written on is exactly the same on both of these machines.

The tests that are breaking will pass on his machine if, instead of using a "Run TestCase" for authenticate, my colleague clones this test case.

On my machine in both cases the result is the same: the tests that were failing remain as failing regardless of whether I'm running a "Run TestCase" or cloning authenticate for the particular test case we're testing.

In fact, I believe my results, with the broken tests, are the correct result.

I know there are many possible causes of this problem, but I thought I'd ask for an opinion in the event that I'm missing something to do with the SoapUI application and you've seen this before.

Thanks for your help,

Tom

6 Replies

  • SmartBear_Suppo's avatar
    SmartBear_Suppo
    Icon for Alumni rankAlumni
    16 years ago
    Hi Tom,

    hmm.. I can't come up with any obvious difference between the two installations.. are they using the same JRE? What kind of authentication is your target service using?

    regards,

    /Ole
    eviware.com
  • Thomas_Fuller's avatar
    Thomas_Fuller
    Occasional Contributor
    16 years ago
    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
  • SmartBear_Suppo's avatar
    SmartBear_Suppo
    Icon for Alumni rankAlumni
    16 years ago
    Hi Tom,

    hmm.. I'm a bit curious on how you are doing authentication and passing the session-id (or cookie?) around.. can you share the project you are using here?

    regards!

    /Ole
    eviware.com
  • Thomas_Fuller's avatar
    Thomas_Fuller
    Occasional Contributor
    16 years ago
    Hi Ole,

    The project file is attached.

    Note that some of the tests pass and others dont, however cases where the test is not passing due to an authentication failure, in almost all cases we have added a "Run [authenticate] TestCase". You may see a clone of authenticate in a few areas -- this is just to get the test running and as far as I know all occurrances should be disabled.

    I'll send you the report as well so you know where to look.

    Thanks for your help,

    Tom
  • Thomas_Fuller's avatar
    Thomas_Fuller
    Occasional Contributor
    16 years ago
    Actually, probably would be easier to just look at the "scanTag with valid data TestCase" or "submitMultimedia TestCase" test cases -- these are both failing, whereas if I clone the "authenticate with valid data TestCase" -> authenticate test step and add it to the "changePassword TestCase" before the changePassword test step, this test will pass (it is also currently failing).

    I'll keep the report unless you ask for it.

    Tom