Contributions
How to ignore disabled tests in SOAPUI commandline
Hi folks, we've got some Soapui tests setup in our build environment. One of the ways we setup our BVTs is through disabling non essential tests in our smoke test suite. This means that we don't have to manage too many projects for the multiple test phases. The problem is that when using the soapui commandline runner the testsuite=disabled, or testcase=disabled settings are not honored. Am I missing something, or should this be classified as a defect? Cheers, Richard13 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.6KViews0likes1CommentDrop down boxes are too short
Hi guys, I'm continually finding myself struggling with the length of the fields in SOAPUI. They don't seem to adapt or reflect the data they contain and therefore make it difficult to select the correct option when selecting from a list if similarly named items. For example, I have a set of requests that are named (rather verbosely) after the request they represent. (This helps with my automated documentation later). When I try to do a property transfer using those requests I have a hard time finding the right one. (see my example attached) This behavior occurs across the product. I feel this could do with some love in your next release! Cheers, - Richard13 years agoPlace ReadyAPI QuestionsReadyAPI Questions3KViews0likes4CommentsGenerating testcase reports from SOAPUI projects
Hi Guys, I've implemented a workaround for creating more readable versions of my test suites for members of my team who don't want to open soapui in order to check the latest set of test cases in my projects. I have a scheduled task that grabs the latest versions of my files from source control, uses an xslt to transform the SOAPUI project xml files and then publishes them to a shared web server which my team can access at any time. I created this process as not all team members want to launch SOAPUI when reviewing testcases and also, it meant we could easily print out lists of the testcases for review/audits. I wasn't able to find a process for doing this. However I've yet to really give the reports aspect of SOAPUI a proper run-through. Anyway, I thought I'd share the xslt with you guys. A) so you could feedback on any issues you find and B) in case it's something other may find useful. <?xml version="1.0" encoding="iso-8859-1"?> <!-- Edited by XMLSpy® --> <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:con="http://eviware.com/soapui/config"> <xsl:output method="html" encoding ="utf-8"/> <xsl:template match="/"> <html> <head> <script type="text/javascript"> function toggleDiv(divid){ var ele = document.getElementById(divid); if(ele.style.display == 'none') { ele.style.display = 'block'; } else { ele.style.display = 'none'; } } </script> <style type="text/css"> h1 { font-family: Helvetica,sans-serif,Arial; background: fixed url(http://photos2.meetupstatic.com/photos/sponsor/5/6/2/3/iab120x90_82051.jpeg) no-repeat top right; background-color:#33A2D2; color:white; margin-top: 2%; padding-top: 10px; padding-left: 10px; font-size: 140%; height:40px; } h2.ex { font-size: 90%; color:white; font-family: Helvetica,Arial,sans-serif; font-weight: 200; line-height: 2.0; text-decoration: none; margin-top: 0%; margin-right: 0%; margin-bottom: 0%; background-color:#797F85; padding-left: 14px; padding-bottom: 0px; cursor:hand; } li.tc { font-size: 90%; font-family: Arial,Helvetica,sans-serif; line-height: 1.4; margin-top: 0%; margin-bottom: 0%; padding-left: 7px; margin-left: -35px; list-style-type:none; } ol.step { font-size: 90%; font-family: Arial,Helvetica,sans-serif; line-height: 1.0; margin-top: 0%; margin-bottom: 0%; padding-left: 7px; margin-left: 25px; } p.descSuite { font-size: 90%; font-family: Arial,Helvetica,sans-serif; line-height: 1.4; border: 1px dotted grey; background-color:#F0F0F0; margin-top: -15px; margin-bottom: 20px; margin-left: 10px; padding-left: 7px; } p.descTc { font-size: 90%; font-family: Arial,Helvetica,sans-serif; line-height: 1.4; border: 1px dotted grey; background-color:#F0F0F0; margin-top: 0px; margin-bottom: 10px; margin-left: 10px; padding-left: 7px; } p.warn { font-size: 90%; font-family: Arial,Helvetica,sans-serif; color:blue; font-weight: 300; margin-top: 10px; } div.help { font-size: 90%; font-family: Arial,Helvetica,sans-serif; line-height: 1.4; border: 1px dotted grey; margin-top: 0%; margin-bottom: 2%; margin-left: 10px; padding: 5px; background-color:#FFFF99; font-size:80%; } </style> </head> <body> <xsl:apply-templates/> <div class="help">This report is generated automatically by a scheduled job running on Richard Fortune's machine. The SOAPUI project files it references are located in sourcecontrol SVN (https://svn.xxx.xxxxxx.xx/svn/network/TEST). These reports are generated daily as the projects they reference are subject to updates.</div> </body> </html> </xsl:template> <xsl:template match="con:soapui-project"> <div><h1>Project Name : <xsl:value-of select="@name"/></h1></div> <xsl:apply-templates/> </xsl:template> <xsl:template match="con:testSuite"> <xsl:if test="con:description=''"> <p class="warn"> (RICHARD - PLEASE PROVIDE A DESCRIPTION!!)</p> </xsl:if> <div id="content" onmousedown="toggleDiv('{position()}');"><h2 class="ex">TestSuite: <xsl:value-of select="@name"/></h2></div> <br> <p class="descSuite"><b>Suite Description: </b><xsl:value-of select="con:description"/></p> </br> <div style="display:none" id="{position()}"><xsl:apply-templates /> </div> </xsl:template> <xsl:template match="con:testCase"> <ul> <li class="tc"><b> (#<xsl:value-of select="position()-3"/>) Testcase: </b><xsl:value-of select="@name"/> </li> <xsl:if test="con:description=''"> <p class="warn">(Gentle reminder Richard - PLEASE PROVIDE A DESCRIPTION!!)</p> </xsl:if> <p class="descTc"> <strong><i>Description:</i></strong> <xsl:value-of select="con:description"/> </p> <ol class="step"> <xsl:for-each select="con:testStep"><li>TestStep: <xsl:value-of select="@name"/> </li></xsl:for-each> </ol> </ul> <xsl:apply-templates /> </xsl:template> <xsl:template match="*"></xsl:template> </xsl:stylesheet> Excuse the styling. I'm not a designer. It was just meant to be quick and easy. Cheers, - Richard13 years agoPlace ReadyAPI QuestionsReadyAPI Questions2KViews0likes0CommentsValidating a WADL response (without using XSD references)
Hi guys, we have an Interesting situation where the response from our API doesn't contain any namespace data, which therefore is lacking the necessary xsd references. As a result we have no way of validating the response we receive when called through SOAPUI. We're using a WADL to define our requests however we have no way of validating the response. Can you advise us of a way to work around this in SOAPui? Cheers, - Richard14 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.3KViews0likes1CommentLoad UI Reports
Hi guys, I'm starting to use the loadui tool to see if I can get some perf stats from our system. I've watched the video clips on the site and have a question which they don't answer. Currently my LoadUI test uses a SOAPUI Project(containing just 1 test case) This test case performs a Get on one of our endpoints and then asserts that the response is not an Error. Should the number of requests increase above 60 per minute our endpoint should return a 500 error stating that the API limit has been exceeded. In this case I would expect the assertions to fail as the response is an error. It does not look like the LoadUI tool is catching failed assertions in a manner I would expect. Could you clarify whether I'm missing something or whether this is a defect? Many thanks, - Richard F14 years agoPlace ReadyAPI QuestionsReadyAPI Questions3.3KViews0likes2CommentsRe: Resource Parameters not applying when empty
Hi Ole, Thanks for the comments. I'm willing move to the Nightly build, but I have concerns about the impact it may have on my testing. How do you guys manage your regular builds? How do you ensure no new issues are introduced with each new Rev? Cheers, - Richard14 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.4KViews0likes0CommentsResource Parameters not applying when empty
Hi Guys, can you tell me if this is an issue or if there is something wrong with the way I'm implementing my resource parameters. When I submit without an Id the request fails ( as you can see from the response window). The RAW request looks like this - GET null HTTP/1.1 Accept-Encoding: gzip,deflate sessionid: 17 If I submit with any type of Id (either valid or otherwise), the request is formed correctly and the endpoint responds appropriately. The RAW request looks as follows: GET http://api-proxy.web/api.xro/2.0/Contacts/s HTTP/1.1 Accept-Encoding: gzip,deflate sessionid: 17 User-Agent: Jakarta Commons-HttpClient/3.1 Host: api-proxy.web NOTE : The GET request is correctly formed. This seems like a defect to me. Id is a parameter, the request should not get set to null if the parameter is not provided. Cheers, Richard14 years agoPlace ReadyAPI QuestionsReadyAPI Questions2.3KViews0likes4CommentsRe: RE: Groovy XML Validation with multiple imported schemas
The issue I'm facing is that our response relies on multiple XSDs for its def. Therefore I need to pull them into some sort of reference array. I've tried several options I've found online but am now blocked. Do you guys have the bandwidth to help out with a sample project using validation with multiple xsds? Cheers, - Richard14 years agoPlace ReadyAPI QuestionsReadyAPI Questions2.4KViews0likes0Comments