Contributions
Customize existing fields in Data Export reports?
I am currently running a daily test via testRunner.bat and saving the results in XML via the Data Export Reports option. There are two customizations I'd like to make to the testSuiteResults.xml file that is generated, one at the test case level and another at the test step level. Each <testCase> node has a <startTime> element that lists the hour, minute, and second the test case was started. I'd like to also include the date, so instead of hh:mm:ss format, I'd like it to be yyyy-MM-dd hh:mm:ss Likewise, each test step has a <result> node with a <started> element that lists the hour, minute, second, and millisecond the step was started. I'd like to also include the date, so instead of hh:MM:ss.sss, I'd like to have yyyy-MM-dd hh:mm:ss.sss Is this possible? I've read through the documentation, and I attempted to substitute my own parameter into the 'TestStepResultsReport.jrxml' file, but to no avail.1.2KViews0likes1CommentRe: GIT Integration
So it's not possible to disable Git while using composite projects? We use compositie projects, and we use Git, but we don't use Git from within ReadyAPI and want to disable it. It is annoying to have to dismiss the pop-up every time we load a project, and can sometimes cause confusion in people that aren't that familiar with ReadyAPI.5 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.4KViews0likes0CommentsRe: Run 2+ SecurityTests from SecurityTest Runner command line?
The solution is to put the word 'call' in front of each testrunner line: cd C:\Program Files\SmartBear\ReadyAPI-1.9.0\bin call securitytestrunner.bat -nSecurityTest1 -fC:\Users\myUser\Desktop\SecureReports -R"Security Issues Report" -E"Default environment" -I C:\Users\myUser\Documents\SoapUI call securitytestrunner.bat -nSecurityTest2 -fC:\Users\myUser\Desktop\SecureReports -R"Security Issues Report" -E"Default environment" -I C:\Users\myUser\Documents\SoapUI7 years agoPlace ReadyAPI QuestionsReadyAPI Questions2.2KViews0likes0CommentsRun 2+ SecurityTests from SecurityTest Runner command line?
I don't see a board for Secure, so I am posting this in the SoapUI board. I am attempting to create a .bat file to execute my security tests. Using the UI in Secure Pro, I can select either 'All' security tests, or a single, specified security test. But what if I want to run more than one, but not all? Is that possible? I tried writing my .bat file like this: cd C:\Program Files\SmartBear\ReadyAPI-1.9.0\bin securitytestrunner.bat -nSecurityTest1 -fC:\Users\myUser\Desktop\SecureReports -R"Security Issues Report" -E"Default environment" -I C:\Users\myUser\Documents\SoapUI securitytestrunner.bat -nSecurityTest2 -fC:\Users\myUser\Desktop\SecureReports -R"Security Issues Report" -E"Default environment" -I C:\Users\myUser\Documents\SoapUI However, after the the first test completes, it saves the report and then the command prompt exits without ever running the second test. Is there a way to stop this from happening, so that it continues on to the next test?Solved7 years agoPlace ReadyAPI QuestionsReadyAPI Questions2.3KViews0likes5CommentsDo Secure Pro tests grab the selected Environment?
I have multiple QA environments setup in SoapUI Pro. I used some SoapUI test cases to create Secure Pro tests. If I change the environment in SoapUI, will the Secure Pro test automatically update? I don't see any way of viewing the request to ensure that Secure Pro is hitting the intended environment.8 years agoPlace ReadyAPI QuestionsReadyAPI Questions739Views0likes0CommentsRefactoring does not update namespace in XPath Assertion's Expected Result
Hello, For many tests, I have used SoapUI Pro to create XPath assertions for entire nodes in the response. When asserting an entire node, rather than the individual elements, a namespace is inserted into the expected response. For example, when asserting the <DateListed> node, which includes elements for Day, Month, Year, and Unparsed, the expected result of the assertion is this: <DateListed xmlns="myurl.com/Web.Services.Interfaces.9.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:s="http://schemas.xmlsoap.org/soap/envelope/"> <Day>12</Day> <Month>12</Month> <Unparsed>12/12/2016</Unparsed> <Year>2016</Year> </DateListed> The problem with this is that I test a versioned WSDL. If I attempt to refactor my 9.0 project to 10.0, the namespace in the expected result is not updated (the namespace in the actual XPathis updated), so the assertion fails because it is looking for 9.0 instead of the new 10.0. I have tried using wildcards, eg. xmlns="myurl.com/Web.Services.Interfaces.*.* but this is not allowed in the namespace. Checking the box to ignore namespace prefixes also does nothing. How can I resolve this?8 years agoPlace ReadyAPI QuestionsReadyAPI Questions868Views0likes1CommentRefactoring WSDL leads to two namespace declarations
I am the lead QA person on a versioned WSDL, and I'm currently trying to figure out how to refactor my SoapUI regression testing project to a new version of the WSDL. When I use the refactoring tool built-in to SoapUI Pro, I end up with two xmlns declarations at the top of each request. As an example, I am trying to go from version 9.0 to 10.0.Here's what I see before and after refactoring: Before: <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns="https://myurl.com/Web.Services.Interfaces.9.0"> After: <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns="https://myurl.com/Web.Services.Interfaces.9.0" xmlns:ns1="https://myurl.com/Web.Services.Interfaces.10.0"> Is there any way I can just replace the namepsace entirely, rather than appending another namespace onto the end, so that the only namespace is ns and it points to the 10.0 version of the WSDL? Thanks!8 years agoPlace ReadyAPI QuestionsReadyAPI Questions640Views0likes0Comments