Contributions
Frustration with "auto save" and "save on exit"
Howdy, I'm frustrated by the file save operations. What I'd really like is for only the "dirty" projects to be saved. I.e. there are projects in my workspace that I haven't touched in months ... but every time I close soapUI they get saved. When I sort by the most recently used projects I get all these dinosaurs resurrected :-). Is there a way to instruct soapUI to ONLY save things that have been modified? Thanks -TAB (yeah, that's what my hair looks like in real life )13 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.6KViews0likes1Comment- 13 years agoPlace ReadyAPI QuestionsReadyAPI Questions655Views0likes0Comments
Overall coverage misses
Howdy, I've just started playing with coverage ... I'm pleased :-). One thing that I'm having trouble with is figuring out what values aren't covered. I run my suite and see overall coverage information ... that's good. And I can dive into a message and see what was present/absent from that particular call ... but I'm looking for an amalgamated rollup that shows overall which entry points have been hit and which are missing. Taking this analogy back to the usual code coverage tools ... they will "paint" my code view so that I can see which areas of code were never touched by any of my test executions. That's what I'm looking for. If I want to improve coverage, what do I need to add to do so. What I hoped to do was to click on the line that has the coverage rollup numbers and see this in the right pane. But the right pane is empty in that case. Thanks -TAB13 years agoPlace ReadyAPI QuestionsReadyAPI Questions1KViews0likes2CommentsAutomatic retry???
I've got cases where I'm sending soapUI calls and I see there are failures on the back-end. But the client works. It looks like soapUI is automatically retrying on certain failures (connection timeouts perhaps?). My dev team is quite surprised that they see so many failures when the soapUI tests are reporting so many successes (without failures). In the past when I've looked into why we seem to send more requests than reported (i.e. the backend reports more requests than soapUI seems to have sent) I concluded there indeed was some retry. I found a similar question, but with no response: viewtopic.php?f=5&t=5120&p=16426&hilit=retry&sid=8c81eeb66e7f15d88f7d6e0100a6064b#p16426 I would appreciate it if you could help me understand what's going on and turn of retry if possible. Thanks -TAB13 years agoPlace ReadyAPI QuestionsReadyAPI Questions3.6KViews0likes3CommentsRunning a single script after each testcase
Howdy, A million years ago I worked for a company with a very advanced test tool set (advanced for a million years ago :-). One of the things that this tool allowed us to do was to define a testcase teardown script at the suite level (meaning only one definition even though there might be dozens of tests) which ran after each testcase. From what I see in soapUI I can define a suite teardown that runs at the end of the suite, or I can define a testcase teardown (which must be defined on each testcase individually). I had hoped that I could use the suite teardown with some logic to figure out which test ran, but the way it looks that only runs if I run the whole test suite. In other words if I jump into a particular testcase and run it, it won't run the suite teardown. Help! I'm trying to avoid having to maintain the same teardown script in dozens of testcases. Thanks -TAB13 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.1KViews0likes1Comment