Contributions
Re: Running test step in TearDown script
Thanks for the reply - just getting back to this. I'm running the test case from the UI. Like I said earlier, the method runTestStepByName executes properly when I run the TearDown script manually by itself. However, it doesn't execute when the test case itself runs. Do you know when this will be fixed? In a nightly build? Thanks!4.4KViews0likes0CommentsRunning test step in TearDown script
Hi All, This may be an easy one - I'm simply trying to build TearDown scripts for my various Test Cases, and all I really need to do is to execute various Test Steps in these scripts. However, I can't seem to get the execution to work - what's the simplest way to do this? I have tried running something like 'testRunner.runTestStepByName("TestStepName")' - and this will work if I execute the TearDown script all by itself - but it does not execute at the end of running the Test Case. Thanks!6.5KViews0likes6CommentsExpecting no request in MockResponse step
I was wondering if anyone has any strategies for verifying the situation where you are expecting your MockResponse step to never receive a request. Our web service sends out data alerts as requests to clients. In a normal case, our MockResponse step would receive the alert and perform some basic assertions on it. We have cases where we want to verify that a client does NOT receive a request. I have tried using the "Script" portion of the MockResponse step, and examining the mockResponse object for a null value, but it looks like the "Script" only gets executed if the MockResponse step actually receives a request. I can also fail the MockResponse step by setting the "Timeout" property to an arbitrary value (the MockResponse never receives a request, so it just times out eventually). However, the test just fails out after the timeout. Thanks to anyone who has any ideas!1.8KViews0likes2Comments- 786Views0likes0Comments
Filename Filter in DataSource Directory step
Hi all, I'm using soapUI Pro 2.02 and I'm working with the DataSource Directory step. Does the Filename Filter work for this functionality? For example, I have a directory that I'm reading from, where I only want to read in *.xml files. I have my filter set to a value of *.xml - however, the DataSource appears to read in all of the files in the directory, not just what I specified in the filter. Also, I wanted to try and filter it on one specific file - MDAL.xml. However, it again seems to be reading in the content of all of the files, not just the one that I wanted. Am I doing something wrong with the filter? Or is this a bug that's been fixed? I am using an older build, Build Date 2008/01/28 15:35 Thanks! Chris2KViews0likes3CommentsRe: Nullpointer when running testrunner on solaris console
I think I have run into a similar issue...trying to run my tests on a Solaris machine via ant, and they will only run if the DISPLAY is set to my local laptop. On Windows there is no such issue. I will wait for the next build...874Views0likes0CommentsRunning testrunner on Solaris
Hi all, I am trying to run testrunner (via an ant script) to run a particular TestSuite on Solaris. I can execute this exact operation without any problems on Windows. On Solaris, I can successfully run the TestSuite through the soapUI GUI in 2 ways - opening up the TestSuite GUI and running it there, and also opening up the Launch TestRunner GUI and running it that way. However, testrunner seems to timeout or get stuck when I try running it from the command line - either by calling it from an ant script, or actually just executing it straight up. The output that I get is always the following: ================================ = = SOAPUI_HOME = /h/soapui-2.0.2 = ================================ soapUI 2.0.2 TestCase Runner Configuring log4j from [jar:file:/h/soapui-2.0.2/bin/soapui-2.0.2.jar!/soapui-log4j.xml] 15:13:20,403 INFO [DefaultSoapUICore] initialized soapui-settings from [/h/soapui-2.0.2/bin/soapui-settings.xml] It never goes any further than this. The fact that I can run it just fine from the GUI indicates to me that I know it can work! But I don't know what else to do at this point... Has anyone run into this before on Solaris? I know that the exact same command line arguments, when called from the "Launch TestRunner" GUI in the application, work without any problem - but when they're called from ant or run manually they do not work. Thanks, Chris2.4KViews0likes0Comments