ContributionsMost RecentMost LikesSolutionsRe: Suite run order other than the order of creationThanks, /Ole; For the meantime we have found manually shifting the xml of our project around to suit our needs for the few times we add new suites. Would it be possible to be notified by email of the completion of this functionality as well? Or, is there some other way we could find out when it has been accomplished? Thanks again, --VRe: An always run capabilityThank you, /Ole; Changing the "Abort on error" flag was successful at accomplishing what we wanted. Thanks for the tip!Re: maven automated "run test case" loses error infoThanks, Ole. I guess my unstated question is also "is there some other way / place that I could go to personally track the progress without your intervention?" A notification when it is done would still be great though :-) I wasn't sure if the visibility was that high (to soap u.i. users) or not -- other than watching for release notes at new version times. Thanks!An always run capabilityHello, Perhaps the functionality doesn't exist, but is there a way to have a 'cleanup-type step' that always gets run in any particular test case even if a previous step fails for whatever reason? example: test case x step 1 - create a record step 2 - pass the generated key to step 3 && 4 step 3 - validation that shouldn't fail (but currently does) step 4 - delete the record test case y (that expects test case x to have cleaned up after itself) ... Notably, one solution seems that we could 'pull out' whatever should always happen into an extra test case (in-between test case x && y) but that would effectively nearly double our number of test cases and be less readable in the end. Is there another SOAP U.I. alternative that could always run step 4 for x regardless of soap faults and other means of failure? If not, should I log that as a feature? Thank you; --VSuite run order other than the order of creationHello, We are also interested in specifying the order that our suites run in as we are having them run in an automated fashion (the maven plugin) and have interdependent suites to manage (referencing the topic here: http://www.eviware.com/component/option ... 01#msg2201). In particular, we have a suite that we need to run first and last. Now the first one has already been manually moved in the xml file but as we add more suites, it looks like we'll have to keep manually moving the last suite to be last in the xml each time. It sounds like you had plans to fix this a while ago and so we're wondering if it has already been accomplished or not; (I searched for the announcement but came up dry) Thanks for the feedback! --VRe: maven automated "run test case" loses error infoThanks for the reply, Ole. Would you be able to contact me when it seems the bug has been fixed? I can be reached at victor.replogle@ontariosystems.com Thank you, --Vmaven automated "run test case" loses error infoHello, We are using the maven 2 plugin to run our SOAP U.I. project in an automated fashion. For normally run test cases, when exceptions get thrown we see a lot of great output such as what was sent in and what exception came back -- the whole xml tree for both request and response. However, if we are using the "Run a test case" step and an exception gets thrown inside that test case...the response back is murky at best: " X test case Failed [Response is a SOAP Fault] Status: FAILED Time Taken: 488 Size: 0 Timestamp: Thu Oct 02 10:36:16 EDT 2008 TestStep: X test case Response is a SOAP Fault " Any chance there's a way to get the rest of the info to float out of there? It is making it hard to debug our test cases. Thank you!