ContributionsMost RecentMost LikesSolutionsRe: [RESOLVED]Maven SoapUI Pro pluginWhen did this change? And why would I need to by a license to use the Maven Pro plugin? Why wouldn't it use my SoapUI app license?Re: Incorrect URL path encoding.I second the request to have this addressed. This is a major issue. If I need to open this as a SoapUI Pro bug to get better visibility I will. ThanksRe: maven in parallelI second Daniel's request-- I have a large maven project broken into multiple modules, each module has it's own set of SoapUI unit tests but running maven3 in parallel build mode fails due to the SoapUI maven plugin not being thread safe. -JRe: Execute eventsTestCase Setup Scripts have a little green right pointing arrow, 'Runs this script' that you can click on that then executes that script even though you are not running the TestCase. It would be nice if that same 'Runs this script' functionality existed for the different event scripts, such as the TestRunListener.beforeRun, or the Script Assertions or Groovy Script TestSteps. In somes cases, such as the events, you might have some initialization stuff (like my beforeRun sets up a bunch of global properties). Runs this script allows me to both test my code works as expected in addition to running arbitrarily. Adding it to Script Assertions and Groovy Script TestSteps allows me to test the code as I'm writing it.Request body chopped on Get DataUsing the Right Click -> Get Data to insert a property expansion within a Request body chops off the last character of the body Tested using 4.5.0Execute eventsIt would be nice if you could execute scripts tied to events such as TestRunListener.beforeRun the same way you can execute TestCase Setup Scripts or Script Assertions or Groovy Script TestStepsTestRunListener.beforeRun triggers during Run TestCaseSeems like incorrect behavior to have the TestRunListener.beforeRun event trigger both when a TestCase is being run AND whenever a Run TestCase TestStep is called. I'm currently using the event to initialize several project variables to default values for use by the TestCase which in some TestCases I override but when a Run TestCase TestStep executes it then resets them back to the default values. Happens in 4.5.0Re: TestCase TestDown script and Run TestCase TestStep returnRight, backwards compatibility Hmmmm.. yeah, anyone that is using tear down to set props for a test step call return would break. Yeah, might need to be an preference setting.Re: TestCase TestDown script and Run TestCase TestStep returnHi, and thanks for putting in the request. I had originally too thought that both cases were valid, but given that you can run a test step script as the last test step you don't really need to make it an option, thus leaving the tear down step as the very last thing that happens. But either way Re: Rename TestCase file errorWill test with the snapshot Note, didn't mentioned it previously, but obviously this needs composite project set.