John_Overbaugh
Occasional Contributor
Joined 18 years ago
User Profile
User Widgets
Contributions
Property - transfer info disappears
This is driving me nuts... I'm using the latest SoapUI (2.0.2) Pro. I have a property in my test suite called holdExpiration and have set it to "2008-04-01T11:11:11.111 which is the default UNIX timedate format. When I use the UI or manually enter the property association (${#TestSuite#holdPlacement}, and then click into another field, what I type/picked using the UI disappears. I've seen this off and on but have generally gotten around it in the past. However, I can't get it to stop today.2.2KViews0likes1CommentRe: Missing Matching Fault
Ole, Some time has passed since. Now we're seeing this EVERYWHERE. I would ask dev to declare these faults, but they're heads-down on other items and prob don't want to roll off user stories to make things more testable. Is it possible to disable/hide these warnings?2KViews0likes0CommentsWhat's the best way to move from server to server?
In my organization, we run a 'swimlane' method of promoting builds from dev to test to stage to prod. This means my SoapUI tests have to be able to run against at least 4 different endpoints. What is the best way to migrate multiple test suites from one endpoint to another? I'm not finding anything really clean or obvious in the documentation. Thanks, John O.2.8KViews0likes1CommentMissing Matching Fault
I have created a test which I expect will fail (I want it to fail). I have added a SOAP Fault assertion, and I've also added an assertion for CONTAINS and the text "does not exist" (which is the text our service returns if the element passed in doesn't exist). When I run it, it passes as expected but I get the following warning: Mon Jan 07 10:31:39 MST 2008:WARN:Missing matching Fault in wsdl for bindingOperation [setBirthMotherInfo] What does this warning mean? Should the faults be contained within our WSDL? John O.4.3KViews0likes3CommentsRe: Errors in interpretation
Hi Ole - sorry for the delay in replying; I was out for the holidays. Yes, yu are correct - if I hard-code the SQL statement and pass that into the function, it works fine. What I'm trying to do is great a simple generic function that returns the count of something. Any other ideas, or is there any additional info I can provide you to see if there's a fix possible? Thanks!! John O.3KViews0likes0CommentsRe: Errors in interpretation
No, I didn't think to try it. So here is my Groovy script then: db.eachRow("SELECT COUNT ('${entryColumnName}') from '${tableName}' WHERE '${entryColumnName}' = '${entryValue}'") { row -> (myCount = row[0])} Unfortunately, it made no difference. It's almost as if soapUI cannot interpret variables in a script name - I think I mentioned that the ONLY variable I can pass in as $variableName is when it's in singlequotes - so '$variableName' works for me. John O.3KViews0likes0CommentsErrors in interpretation
I'm working with Groovy scripts and soapUI. I have a Groovy script full of helper functions, and I've been creating a new helper function which is SELECT COUNT (columnName) FROM tableName WHERE columnName = 'value' As you can see in the attached code, my helper function takes the columnName, tableName, entryValue, as well as a reference to the log and a binary (whether to throw an exception or error silently). All these parameters have been inserted into the SQL statement using $tableName and the likes: db.eachRow("SELECT COUNT ('$entryColumnName') from '$tableName' WHERE '$entryColumnName' = '$entryValue'") I have also simply built the query string: myQuery = "SELECT COUNT ($entryColumnName) from $tableName WHERE $entryColumnName = '$entryValue'" In all cases, when I reference the function from within soapUI, I get a SQL exception "invalid table name". I can literally copy the SQL statement and run it in SQL Developer and it succeeds. And if I hard-code values (instead of $tableName and other variables), it succeeds. There seems to be a problem interpreting variables when building a SQL string. It has worked consistently when it interprets '$condition' in a SQL statement substring enclosed in single-quotes; this is the first time I've tried to create an entire SQL statement this way. Any help = much appreciated. I've banged me head against the wall all day on this one. Very frustrating.7.6KViews0likes9Comments