[Resolv.]Data-driven test with multiple logins exception ..

So where is your test case failing: at a datasource step, request step, or datasource loop step?

If you open your datasource that is pointing to the XML File, press the green play button. Do all the excel rows get populated?

Thanks,
Michael Giller
SmartBear Software

My apologies for not making that more clear in my original posting. It appears that it fails while trying to initiate the second login. There is no issue with the datasource. If I hate the green play button on the datasource the rows get populated completely correctly. I'm attaching a picture of the test failure.

Hmm. The screenshot confirms the error but doesn't shed much light into why it happens.

In your "TestCase Log" tab, double click the failed "getHomepage" test step. That should show you the request as it was sent and the response received. I would confirm that it has the values from second row of DataSource populated in the request.

You can also use Test Debugging functionality to go step-by-step in recreating the issue: http://www.soapui.org/Functional-Testin ... gging.html

Thanks,
Michael Giller
SmartBear Software

Clicking on the "TestCase Log" tab "getHomepage" test step, shows nothing for the request. That is why I assumed there was an issue regarding the logout and "Maintain Http Session" setting. Also, if I remove the logout step, everything seems to work fine, which is odd, because I would have expected the subsequent requests to be conflicted as to which user was logged in, so I dont understand how that works.

I will try and test debugging functionality to see if that shed's any light.

So, running the test suite through in debug mode, caused the stack trace to offer some additional information. It appears that my original assumption is correct, that due to the "Maintain Http session" option, logging out and then logging back in is causing issues. Here is the more complete stack trace that now includes a "caused by":

Mon Oct 14 10:22:50 EDT 2013:ERROR:org.apache.http.client.ClientProtocolException
org.apache.http.client.ClientProtocolException
at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:822)
at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:754)
at com.eviware.soapui.impl.wsdl.support.http.HttpClientSupport$Helper.execute(HttpClientSupport.java:246)
at com.eviware.soapui.impl.wsdl.support.http.HttpClientSupport.execute(HttpClientSupport.java:356)
at com.eviware.soapui.impl.wsdl.submit.transports.http.HttpClientRequestTransport.submitRequest(HttpClientRequestTransport.java:317)
at com.eviware.soapui.impl.wsdl.submit.transports.http.HttpClientRequestTransport.followRedirects(HttpClientRequestTransport.java:357)
at com.eviware.soapui.impl.wsdl.submit.transports.http.HttpClientRequestTransport.sendRequest(HttpClientRequestTransport.java:249)
at com.eviware.soapui.impl.wsdl.WsdlSubmit.run(WsdlSubmit.java:123)
at com.eviware.soapui.impl.wsdl.WsdlSubmit.submitRequest(WsdlSubmit.java:76)
at com.eviware.soapui.impl.rest.RestRequest.submit(RestRequest.java:209)
at com.eviware.soapui.impl.wsdl.teststeps.RestTestRequestStep.run(RestTestRequestStep.java:898)
at com.eviware.soapui.impl.wsdl.support.AbstractTestCaseRunner.runTestStep(AbstractTestCaseRunner.java:239)
at com.eviware.soapui.debug.DebugTestCaseRunner.runTestStep(SourceFile:50)
at com.eviware.soapui.impl.wsdl.testcase.WsdlTestCaseRunner.runCurrentTestStep(WsdlTestCaseRunner.java:48)
at com.eviware.soapui.impl.wsdl.support.AbstractTestCaseRunner.internalRun(AbstractTestCaseRunner.java:148)
at com.eviware.soapui.impl.wsdl.support.AbstractTestCaseRunner.internalRun(AbstractTestCaseRunner.java:43)
at com.eviware.soapui.impl.wsdl.support.AbstractTestRunner.run(AbstractTestRunner.java:135)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: org.apache.http.client.CircularRedirectException: Circular redirect to 'http://xxxxx/yyyy/zzzzzz'
at org.apache.http.impl.client.DefaultRedirectStrategy.getLocationURI(DefaultRedirectStrategy.java:168)
at org.apache.http.impl.client.DefaultRedirectStrategy.getRedirect(DefaultRedirectStrategy.java:193)
at org.apache.http.impl.client.DefaultRequestDirector.handleResponse(DefaultRequestDirector.java:1021)
at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:482)
at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:820)
... 22 more

So here is what is happening:
1) I'm calling http://www.myhomepage.com to get the homepage content
2) using information from this homepage call to then login with account A
3) while logged in with this account, making a call to api 1 and api 2
4) log out account A
5) call http://www.myhomepage.com to try and start a new session

At step 5 when the call to http://www.myhomepage.com is being called, it's being redirected to http://www.myhomepage.com/Home just like would happen in a browser if you were to navigate to http://www.myhomepage.com when you already had a session logged in. So, my question would be, with the "Maintain Http session" option checked globally for the Test Case, is it possible to have multiple logins and logouts? As another bit of information, the logout appears to work correctly. If I look at the "HTML" representation of the response of the logout call, it is correctly showing the login page.

Interesting. So you still need the "Maintain HTTP Session" option checked to maintain it from step 1 to step 2, but it interferes for different loops.

What I would recommend is resetting the Cookies at the end of each loop. So try the following:
- add a Groovy script step right before the "DataSource Loop" step
- add the following code

import com.eviware.soapui.impl.wsdl.support.http.HttpClientSupport
import org.apache.http.impl.client.BasicCookieStore
def mySoapUIHttpClient = HttpClientSupport.getHttpClient()
def myCookieStore = mySoapUIHttpClient.getCookieStore()

myCookieStore.clear()

This is from a very informative post that Siking's blog about SoapUI cookie management:
http://siking.wordpress.com/2013/07/25/ ... anagement/

Thanks,
Michael Giller
SmartBear Software

That still isnt helping either. Still having the same issue. I'd like to try splitting the login step into it's own test case but keep the DataSource in the Api test case. Is it possible to have a groovy script in the Login test case that would be able to reference the DataSource. Currently, when referencing the DataSource from a Groovy script that exists in the same test case, I use something like this:

context.expand('${DataSource#User}')

Is what I'm asking possible? If so, what would the syntax be?

As I'm still trying to conquer this, is there a way within groovy to manually reset/create a new session? Something like session.invalidate? I've been looking around but can't seem to find a way to do this.

Hi,

just another idea - did you try to set the ClientPNames.ALLOW_CIRCULAR_REDIRECTS parameter on the httpClient?

import com.eviware.soapui.impl.wsdl.support.http.HttpClientSupport
HttpClientSupport.getHttpClient().getParams().setParameter( ClientPNames.ALLOW_CIRCULAR_REDIRECTS, true )

Regards,
Anders
SmartBear Sweden

I wasnt doing anything like that. I tried adding those 2 lines to one of the groovy scripts at the beginning of my test case and I get the following error:

groovy.lang.MissingPropertyException: No such property: ClientPNames for class: Script9

I wasnt previously doing anything with an http client in the script. Is there something else I need to define?