truetruefalsetruetrueMultiple PagesC:\dev\htmlreportssoapUI Reporthttp://www.soapui.org/samplehttp://127.0.0.1:8088/mockSampleServiceSoapBindingUTF-8http://127.0.0.1:8088/mockSampleServiceSoapBinding Login Login123 ]]>UTF-8http://127.0.0.1:8088/mockSampleServiceSoapBinding 21974891784000294 ]]><xml-fragment/>UTF-8http://127.0.0.1:8088/mockSampleServiceSoapBinding 15350144624459006 ? ]]>UTF-8http://127.0.0.1:8088/mockSampleServiceSoapBinding ? ? ]]>file:C:\eviware\Projects\WSDL\sample.wsdl http://schemas.xmlsoap.org/wsdl/This is a sample TestSuite. It contains a number of TestCases Illustrating a number of principles with soapUI. Try each test and read the descriptions.C:\dev\testreporttrueFramesC:\dev\testreportMultiple PagestruetruefalsetruetrueDefault TitleSEQUENTIALTestCase: Simple Login and Logout This one is easy... The test will first login and then it will logout. :-) We are using a Property Transfer Step to move password and user name from a Properties Step to the Request and a second Property Transfer Step to move the sessionID we got in the login response to the logout request..Default TitlkjleUsernameLoginn${=String.valueOf(Math.random()).substring( 0, 5 )}PasswordLoginn123TransferUserUsernameProperties: Username and PasswordRequestTest Request: logindeclare namespace sam='http://www.example.org/sample/'; //sam:login/usernameTransferPassPasswordProperties: Username and PasswordRequestTest Request: logindeclare namespace sam='http://www.example.org/sample/'; //sam:login/passwordSampleServiceSoapBindinglogin<xml-fragment/>UTF-8http://127.0.0.1:8088/mockSampleServiceSoapBinding Loginn${=String.valueOf(Math.random()).substring( 0, 5 )} Loginn123 ]]>MoveSessionIdResponseTest Request: logindeclare namespace sam='http://www.example.org/sample/'; //sam:loginResponse/sessionidRequestTest Request: logoutdeclare namespace sam='http://www.example.org/sample/'; //sam:logout/sessionidSampleServiceSoapBindinglogoutUTF-8http://127.0.0.1:8088/mockSampleServiceSoapBinding 6653469643556499 ]]>Default Titlefalse50250falsetrue-160TIMESimple1000falsefalsetrue500falseReportTitle${=testCase.name}TestCase: Simple Login and Logout This one is easy and a little tighter than "Simple Login and Logout w. Properties Steps" The test will first login and then it will logout. :-) We are using a Property Transfer Step to move password and user name from a Properties Step to the Request and a second Property Transfer Step to move the sessionID we got in the login response to the logout request..UsernameLoginn${=String.valueOf(Math.random()).substring( 0, 5 )}PasswordLoginu123SampleServiceSoapBindingloginUTF-8http://127.0.0.1:8088/mockSampleServiceSoapBinding ${Properties: Username and Password#Username} ${Properties: Username and Password#Password} ]]>SampleServiceSoapBindinglogoutUTF-8http://127.0.0.1:8088/mockSampleServiceSoapBinding ${Test Request: login#Response#//sam:loginResponse/sessionid} ]]>TestCase: Simple Login and Logout This one is a bit wonky, but has its reasons. What we are testing is that we are able to login again after a logout. The test will: 1) login 2) logout 3) login again 4) logout again The last step is there in order for us to be able to run the test continuously.UsernameLoginn${=String.valueOf(Math.random()).substring( 0, 5 )}PasswordLoginu123SampleServiceSoapBindingloginUTF-8http://127.0.0.1:8088/mockSampleServiceSoapBinding ${Properties: Username and Password#Username} ${Properties: Username and Password#Password} ]]>SampleServiceSoapBindinglogoutUTF-8http://127.0.0.1:8088/mockSampleServiceSoapBinding ${Test Request: login#Response#//sam:loginResponse/sessionid} ]]>SampleServiceSoapBindingloginUTF-8http://127.0.0.1:8088/mockSampleServiceSoapBinding ${Properties: Username and Password#Username} ${Properties: Username and Password#Password} ]]>SampleServiceSoapBindinglogoutUTF-8http://127.0.0.1:8088/mockSampleServiceSoapBinding ${Test Request: login again#Response#//sam:loginResponse/sessionid} ]]>TestCase: Simple Search TestCase The test extends the previous TastCases by doing a simple search between login and logout. We are using a Property Transfer Step to move password and user name from a Properties Step to the Request and a second Property Transfer Step to move the sessionID we got in the login response to the logout request..UsernameLogini${=String.valueOf(Math.random()).substring( 0, 5 )}PasswordLogini123SearchPhraseItem 1TransferUserUsernameProperties: Username and PasswordRequestTest Request: logindeclare namespace sam='http://www.example.org/sample/'; //sam:login/usernameTransferPassPasswordProperties: Username and PasswordRequestTest Request: logindeclare namespace sam='http://www.example.org/sample/'; //sam:login/passwordSampleServiceSoapBindinglogin<xml-fragment/>UTF-8http://127.0.0.1:8088/mockSampleServiceSoapBinding Logini${=String.valueOf(Math.random()).substring( 0, 5 )} Logini123 ]]>MoveSessionIdResponseTest Request: logindeclare namespace sam='http://www.example.org/sample/'; //sam:loginResponse/sessionidRequestTest Request: logoutdeclare namespace sam='http://www.example.org/sample/'; //sam:logout/sessionidmoveSessionID SearchResponseTest Request: logindeclare namespace sam='http://www.example.org/sample/'; //sam:loginResponse/sessionidRequestTest Request: searchdeclare namespace sam='http://www.example.org/sample/'; //sam:search/sessionidMoveSearchstringSearchPhraseProperties: Username and PasswordRequestTest Request: searchdeclare namespace sam='http://www.example.org/sample/'; //sam:search/searchstringSampleServiceSoapBindingsearch<xml-fragment/>UTF-8http://127.0.0.1:8088/mockSampleServiceSoapBinding 3893759046191424 Item 1 ]]>SampleServiceSoapBindinglogoutUTF-8http://127.0.0.1:8088/mockSampleServiceSoapBinding 3893759046191424 ]]>import soapui.demo.subreport.SystemPropertiesSubReport if( !report.hasSubReport( "SystemProperties" )) { report.addSubReport( new SystemPropertiesSubReport( testSuite )) } This is a complementary TestSuite that illustrates something important. Do not only test that your Web Service works under the right conditions, also test that it work under the wrong ones. One of the strengths of soapUI is the ability do quickly create a number of destructive tests, that confirms that the your Web Service handles input errors, abuse, input faults etc. correctly.SEQUENTIALNow, what's this? TestCases that we want to fail? Yes, sometimes it's a great idea to test that the Web Service fail when it should and fail correctly. Therefore the TestCase will pass if we get fails for every test in the Case. These tests are for login alone.SampleServiceSoapBindingloginUTF-8http://127.0.0.1:8088/mockSampleServiceSoapBinding Logi Loginn123 ]]>declare namespace sam='http://www.example.org/sample/'; //detail/sam:loginFaultThe login credentials are invalidfalseSampleServiceSoapBindingloginUTF-8http://127.0.0.1:8088/mockSampleServiceSoapBinding Loginn Loginn ]]>declare namespace sam='http://www.example.org/sample/'; //detail/sam:loginFaultThe login credentials are invalidfalseSampleServiceSoapBindingloginUTF-8http://127.0.0.1:8088/mockSampleServiceSoapBinding Loginnnnnnsdfgdfgf Loginnnnnn123 ]]>declare namespace sam='http://www.example.org/sample/'; //detail/sam:loginFaultThe login credentials are invalidfalseSampleServiceSoapBindingloginUTF-8http://127.0.0.1:8088/mockSampleServiceSoapBinding Log Log123 ]]>declare namespace sam='http://www.example.org/sample/'; //detail/sam:loginFaultThe login credentials are invalidfalseSampleServiceSoapBindingloginUTF-8http://127.0.0.1:8088/mockSampleServiceSoapBinding Login Login123 ]]>SampleServiceSoapBindingloginUTF-8http://127.0.0.1:8088/mockSampleServiceSoapBinding Login Login123 ]]>//faultstringAlready LoginfalseSampleServiceSoapBindinglogoutUTF-8http://127.0.0.1:8088/mockSampleServiceSoapBinding ${Test Request: Double Login step 1 (SUCCESS)#Response#//sam:loginResponse/sessionid} ]]>declare namespace sam='http://www.example.org/sample/'; //sam:logoutResponse/sessioninfoOKfalseAnother batch of TestCases that we want to fail? These tests expands on what we did with "TestCase: Invalid Login" and shows some important test that you always should have. 1) If you have a Web Service that depends on logging in, always make sure that nothing can be done wothout logging in. Don't make one test, make several. 2) If you have a Web Service that depends on logging in, create a number of test with the user logged in. 3) Create SQL injections test. Sure this should not never ever happend, but it does... And when it does it is bad. It is easy to create with soapUI and will make you sleep easier at night. 4) Always test what happends when you try to make a call quickly after logging out. Session29711622719335506SampleServiceSoapBindingsearch<xml-fragment/>UTF-8http://127.0.0.1:8088/mockSampleServiceSoapBinding ${Correct Session Property#Session} Item 4 ]]>//faultstringInvalid Session IdfalseSampleServiceSoapBindingsearch<xml-fragment/>UTF-8http://127.0.0.1:8088/mockSampleServiceSoapBinding ${Correct Session Property#Session} Item 7 ]]>//faultstringInvalid Session IdfalseSampleServiceSoapBindingsearch<xml-fragment/>UTF-8http://127.0.0.1:8088/mockSampleServiceSoapBinding ${Correct Session Property#Session} ]]>//faultstringInvalid Session IdfalseSampleServiceSoapBindingsearch<xml-fragment/>UTF-8http://127.0.0.1:8088/mockSampleServiceSoapBinding 6767676767676 Item 1 ]]>//faultstringInvalid Session IdfalseSampleServiceSoapBindingsearch<xml-fragment/>UTF-8http://127.0.0.1:8088/mockSampleServiceSoapBinding ${Correct Session Property#Session} Select * from Customers ]]>//faultstringInvalid Session IdfalseSampleServiceSoapBindingsearch<xml-fragment/>UTF-8http://127.0.0.1:8088/mockSampleServiceSoapBinding Select * from Customers Item 2 ]]>//faultstringInvalid Session IdfalseSampleServiceSoapBindingsearch<xml-fragment/>UTF-8http://127.0.0.1:8088/mockSampleServiceSoapBinding ${Correct Session Property#Session} ${Correct Session Property#Session} Item 2 ]]>//faultstringMissing operation for soapAction [http://www.example.org/sample/search] and body element [{http://www.example.org/sample/}search] with SOAP Version [SOAP 1.1]falsefalseSampleServiceSoapBindingloginUTF-8http://127.0.0.1:8088/mockSampleServiceSoapBinding Login Login123 ]]>SampleServiceSoapBindingsearch<xml-fragment/>UTF-8http://127.0.0.1:8088/mockSampleServiceSoapBinding ${Test Request: Login#Response#//sam:loginResponse/sessionid} Item 7 ]]>Unknown SearchfalseSampleServiceSoapBindingsearch<xml-fragment/>UTF-8http://127.0.0.1:8088/mockSampleServiceSoapBinding ${Test Request: Login#Response#//sam:loginResponse/sessionid} ]]>//faultstringUnknown Search StringfalseSampleServiceSoapBindingsearch<xml-fragment/>UTF-8http://127.0.0.1:8088/mockSampleServiceSoapBinding 6767676767676 Item 1 ]]>//faultstringInvalid Session IdfalseSampleServiceSoapBindingsearch<xml-fragment/>UTF-8http://127.0.0.1:8088/mockSampleServiceSoapBinding ${Test Request: Login#Response#//sam:loginResponse/sessionid} Select * from Customers ]]>//faultstringUnknown Search StringfalseSampleServiceSoapBindingsearch<xml-fragment/>UTF-8http://127.0.0.1:8088/mockSampleServiceSoapBinding Select * from Customers Item 2 ]]>//faultstringInvalid Session IdfalseSampleServiceSoapBindingsearch<xml-fragment/>UTF-8http://127.0.0.1:8088/mockSampleServiceSoapBinding ${Test Request: Login#Response#//sam:loginResponse/sessionid} ${Test Request: Login#Response#//sam:loginResponse/sessionid} Item 2 ]]>//faultstringMissing operation for soapAction [http://www.example.org/sample/search] and body element [{http://www.example.org/sample/}search] with SOAP Version [SOAP 1.1]falsefalseSampleServiceSoapBindinglogoutUTF-8http://127.0.0.1:8088/mockSampleServiceSoapBinding ${Test Request: Login#Response#//sam:loginResponse/sessionid} ]]>declare namespace sam='http://www.example.org/sample/'; //sam:logoutResponse/sessioninfoOKfalseSampleServiceSoapBindingsearch<xml-fragment/>UTF-8http://127.0.0.1:8088/mockSampleServiceSoapBinding ${Correct Session Property#Session} Item 4 ]]>//faultstringInvalid Session IdfalseHere is an interesting TestCase. The actual TestCase itself is not that interesting, but we've used it in order to test how the Web Service handles load. AND... The second LoadTest "LoadTest with Multiple Tests (will fail)" DOES fail. Why does it fail and not the first? This is because in the first test we have just one simple thread and in the second we have a whopping ten. What have we achieved? Our Web Service is not thread safe! Bug Found! SampleServiceSoapBindingloginUTF-8http://127.0.0.1:8088/mockSampleServiceSoapBinding Login${=String.valueOf(Math.random()).substring( 0, 5 )} Login123 ]]>SampleServiceSoapBindinglogoutUTF-8http://127.0.0.1:8088/mockSampleServiceSoapBinding ${Test Request: Login#Response#//sam:loginResponse/sessionid} ]]>declare namespace sam='http://www.example.org/sample/'; //sam:logoutResponse/sessioninfoOKfalseSampleServiceSoapBindingsearch<xml-fragment/>UTF-8http://127.0.0.1:8088/mockSampleServiceSoapBinding ${Test Request: Login#Response#//sam:loginResponse/sessionid} Item 4 ]]>//faultstringInvalid Session Idfalsefalse10250falsetrue-160TIMESimple100true500false100250falsetrue-160TIMESimpleAfter 30 errors, stop300.0- Any -100true500URLSEQUENTIALTestCase: Search and Buy TestCase This test is the first expanded TestCase. It basically tests our entire MockService by doing the following. 1) Logging in 2) Searching for all items in stock 3) Choosing the first items and Buying it 4) Logging out We also have added LoadTests of all "Strategies" 1) Simple 2) Variance 3) Burst 4) Thread The thread strategy will produce errors. We will go into that further in the TestCase "TestCase: Searching after Logging out LoadTests" in the TestSuite "Sample TestSuite fails if we don't get faults"UsernameLogini${=String.valueOf(Math.random()).substring( 0, 5 )}PasswordLogini123SearchPhraseItem 1SampleServiceSoapBindingloginUTF-8http://127.0.0.1:8088/mockSampleServiceSoapBinding ${Properties: Username and Password#Username} ${Properties: Username and Password#Password} ]]>SampleServiceSoapBindingsearch<xml-fragment/>UTF-8http://127.0.0.1:8088/mockSampleServiceSoapBinding ${Test Request: login#Response#//sam:loginResponse/sessionid} all ]]>declare namespace sam='http://www.example.org/sample/'; //sam:searchResponse[1]/sam:searchResponse/item[3]/descriptionOne towel. Massively useful thing. Impress the strags with this amazing cloth!falseSampleServiceSoapBindingbuyUTF-8http://127.0.0.1:8088/mockSampleServiceSoapBinding ${Test Request: login#Response#//sam:loginResponse/sessionid} ${Test Request: search#Response#//sam:searchResponse/sam:searchResponse/item[id="Item 5"]/id} ]]>declare namespace sam='http://www.example.org/sample/'; //sam:buyResponse/purchasestatus/expectedDeliveryYou should already have it.falseSampleServiceSoapBindinglogoutUTF-8http://127.0.0.1:8088/mockSampleServiceSoapBinding ${Test Request: login#Response#//sam:loginResponse/sessionid} ]]>false10250falsetrue-130TIMESimple100true500false10250falsetrue-130TIMEVariance50000.5100true500false10250falsetrue-130TIMEBurst50005000100true500false20250falsetrue-130TIMEThread12100true500This TestCase shows some interesting assertions. Check out the search TestStep, there are two assertions "XPath retrieve sibling value" and "XPath Match More Than Less Than" that shows some interesting ways of using XPath.UsernameLogini${=String.valueOf(Math.random()).substring( 0, 5 )}PasswordLogini123SearchPhraseItem 1ItemItem 3Wanted At Least2.50Wanted at most3.50Sibling2.99SampleServiceSoapBindingloginUTF-8http://127.0.0.1:8088/mockSampleServiceSoapBinding ${Properties: Username and Password#Username} ${Properties: Username and Password#Password} ]]>SampleServiceSoapBindingsearch<xml-fragment/>UTF-8http://127.0.0.1:8088/mockSampleServiceSoapBinding ${Test Request: login#Response#//sam:loginResponse/sessionid} all ]]>declare namespace sam='http://www.example.org/sample/'; //sam:searchResponse[1]/sam:searchResponse/item[3]/descriptionOne towel. Massively useful thing. Impress the strags with this amazing cloth!falsedeclare namespace sam='http://www.example.org/sample/'; //sam:searchResponse[1]/sam:searchResponse/item[id="${Properties: Wanted Response#Item}"]/price >= ("${Properties: Wanted Response#Wanted At Least}") and //sam:searchResponse[1]/sam:searchResponse/item[id="${Properties: Wanted Response#Item}"]/price <= ("${Properties: Wanted Response#Wanted At Most}" )truefalsedeclare namespace sam='http://www.example.org/sample/'; //sam:searchResponse[1]/sam:searchResponse/item[price="${Properties: Wanted Response#Sibling}"]/id${Properties: Wanted Response#Item}falseSampleServiceSoapBindinglogoutUTF-8http://127.0.0.1:8088/mockSampleServiceSoapBinding ${Test Request: login#Response#//sam:loginResponse/sessionid} ]]>falsedef groovyUtils = new com.eviware.soapui.support.GroovyUtils( context ) def holder = groovyUtils.getXmlHolder( mockRequest.requestContent ) def username = holder.getNodeValue( "//username" ) def password = holder.getNodeValue( "//password" ) def sum = username + password // validate if( sum.length() > 25 || sum.length() < 10 || !username.startsWith("Login") || !password.endsWith( "123" )) return "Invalid Login Fault" if( context.hasProperty( sum )) return "Already Logged In Fault" // seems ok def sessionid = String.valueOf( Math.random() ).substring( 2 ) context.setProperty( sum, sessionid ) context.setProperty( sessionid, sum ) requestContext.sessionid = sessionid return "Ok Response" SCRIPTOk Response ${sessionid} ]]> Client Invalid Login The login credentials are invalid ]]> Client Already Login The specified credentials are already logged in ]]>def groovyUtils = new com.eviware.soapui.support.GroovyUtils( context ) def holder = groovyUtils.getXmlHolder( mockRequest.requestContent ) def sessionid = holder.getNodeValue( "//sessionid" ) // check if( !context.hasProperty( sessionid )) return "Invalid Session Id Fault" // logout context.removeProperty( context.getProperty( sessionid )) context.removeProperty( sessionid ) requestContext.sessioninfo = "OK" return "Ok Response" SCRIPTResponse 1 ${sessioninfo} ]]> Client Invalid Session Id ]]>def groovyUtils = new com.eviware.soapui.support.GroovyUtils( context ) def holder = groovyUtils.getXmlHolder( mockRequest.requestContent ) def sessionid = holder.getNodeValue( "//sessionid" ) // check if( !context.hasProperty( sessionid )) return "Invalid Session Id Fault" def searchstring = holder.getNodeValue( "//searchstring" ) if (searchstring == "all") return "WildCard Response" else if (searchstring == "Item 1") return "Item 1 Response" else if (searchstring == "Item 2") return "Item 2 Response" else if (searchstring == "Item 3") return "Item 3 Response" else if (searchstring == "Item 4") return "Item 3 Response" else if (searchstring == "Item 5") return "Item 5 Response" else return "Unknown Response" return "Search Response"SCRIPTResponse 1context.item4description = Math.random() > 0.9 ? "garbage" : "Item nr 4" 1 One handy protocol droid. 1 2 Item nr 2 2 3 Item nr 3 3 4 ${item4description} 4 5 Item nr 5 5 ]]> Client Invalid Session Id ]]>context.item4description = Math.random() > 0.9 ? "garbage" : "Item nr 4" Item 1 One handy protocol droid. This droid is fluent in over six million forms of communication and has a lovely golden color. Built by an enthusiast. Mindwiped only once. Can be carried on your back. 1 ]]>context.item4description = Math.random() > 0.9 ? "garbage" : "Item nr 4" Item 2 Box of chocolate with several popular items. Covered in Glucose. Recommended safety distance when eating Spring Surprise, 10 feet. 1.99 ]]>context.item4description = Math.random() > 0.9 ? "garbage" : "Item nr 4" Item 3 One towel. Massively useful thing. Impress the strags with this amazing cloth! 2.99 ]]>context.item4description = Math.random() > 0.9 ? "garbage" : "Item nr 4" item 4 Ono-Sendai 7. The newest cowboy tech from Hosaka. Break the ICE with this conversation piece. 4.99 ]]>context.item4description = Math.random() > 0.9 ? "garbage" : "Item nr 4" item 5 soapui Pro 1.7.5. Necessary when testing Web Services. 349 ]]>context.item4description = Math.random() > 0.9 ? "garbage" : "Item nr 4" Server No Result The search returned no items ]]> Client Unknown Search String ]]>context.item4description = Math.random() > 0.9 ? "garbage" : "Item nr 4" Item 1 One handy protocol droid. This droid is fluent in over six million forms of communication and has a lovely golden color. Built by an enthusiast. Mindwiped only once. Can be carried on your back. 1 Item 2 Box of chocolate with several popular items. Covered in Glucose. Recommended safety distance when eating Spring Surprise, 10 feet. 1.99 Item 3 One towel. Massively useful thing. Impress the strags with this amazing cloth! 2.99 Item 4 Ono-Sendai 7. The newest cowboy tech from Hosaka. Break the ICE with this conversation piece. 4.99 Item 5 soapui Pro 1.7.5. Necessary when testing Web Services. 349 ]]>def groovyUtils = new com.eviware.soapui.support.GroovyUtils( context ) def holder = groovyUtils.getXmlHolder( mockRequest.requestContent ) def sessionid = holder.getNodeValue( "//sessionid" ) // check if( !context.hasProperty( sessionid )) return "Invalid Session Id Fault" def buystring = holder.getNodeValue( "//buystring" ) if (buystring == "all") return "WildCard Response" else if (buystring == "Item 1") return "Item 1 Response" else if (buystring == "Item 2") return "Item 2 Response" else if (buystring == "Item 3") return "Item 3 Response" else if (buystring == "Item 4") return "Item 3 Response" else if (buystring == "Item 5") return "Item 5 Response" else return "Unknown Response" return "Search Response"SCRIPTBuy Response ? ? ? ]]> Item 1 1 unit 2000 years from now ]]> Item 2 10 000 boxes 1 week ]]> Item 3 4 towels Any day now... ]]> Item 4 1 unit In the near future. ]]> Item 5 1 license You should already have it. ]]> Client Invalid Session Id ]]> ? ? ? ]]> Item 1 1 unit 2000 years from now Item 2 10 000 boxes 1 week Item 3 4 towels Any day now... Item 4 1 unit In the near future. ' Item 5 1 license You should already have it. ¨ ]]>Some Propertywith a value SystemPropertiesReport /home/robert/soapui/bin/reports/subreports/loadtest/LoadTestLog.jrxml COMMON SUBREPORT LoadTestLog Name Value System Properties $F{name} $F{value} ]]> NO DESC PROJECT