TestEngine + Jenkins Plugin: Execute list of Project/Suite/Case SoapUI tests
In their current implementation 1.) the TestEngine needs to be provided a zip with all required files by the calling client 2.) the TestEngine Jenkins plugin will execute one Project/Suite/Case per Jenkins job Problem: This setup does not scale to execute many Project/Suite/Case SoapUI tests in a row Suggestion: ad 1.) a.) Provide TestEngine the ability to access/checkout GIT repos containing SoapUI Projects b.) Add an API to TestEngine that will take the Project/Suite/Case/... parameters and pick all required files from above local checkout area --> Like this no files need to be created/transfered to the TestEngine server What still needs to be done is the specification of the list of Project/Suite/Case to be executed. This could be provided by one or more config files maintained in the GIT repo(s) ad 2.) In case the TestEngine runs on the Jenkins slave(s), the Jenkins job could - checkout the GIT repo(s) - locate the config file(s) containing the list of /Project/Suite/Case SoapUI Tests in the checkout area (e.g. via parameter) - loop the config file(s) calling the TestEngine API with Project/Suite/Case/... parameters --> like this - The TestEngine is running as a server (contrary to testruner.sh) - The invocation of many Project/Suite/Case's will run with minimal overhead (presumably msecs instead of secs) - all required files are taken from a repo -> any updates propagate to TestEngine automatically Remark: This type of automated execution of SoapUI Test from different Project/Suite/Case needs to complemented with a suitable test report (e.g. csv file with Project/Suite/Case/Step, timeStamp, Status, ExecTime, ErrorMsg, ...Script library interoperability, javaDoc, refactoring, search & autocomplete in all scripts
I'm sorry, but to me the idea mentioned Intellisense-on-custom-groovy-librarybyrunzTHalmost 6 years ago (wow!) is still not implemented, even though labeled as such. In current version ReadyAPI 3.10.0 I still do not have the kind of intellisense I would like to see: - no hassling with .jar files, I want to have interoperability with all of the groovy files in my custom script library like defined in the ReadyAPI project. A restart of some sort I can understand, but when we need to start with importing files we know this is something that will only work locally and for that version. - PLEASE: Proper IDE capabilities, like auto-complete, auto-formatting, code error detections (missing curly bracket for instance), renaming/refactoring, search (and replace),... in ALL scripts (setup scripts, groovy tests steps, tear downs, script library,...). It is such a breeze when I use other (front-end) test automation tools to see that I can do those things, but then return to ReadyAPI and feel like an IT-guy from the 90's. - I'd like proper javaDoc documentations to know what each method does. Currently I can only see what parameter type(s) I need to provide, but not what this method actually does or what I can expect to be returned. Scripting is such an extra weapon to be used in ReadyAPI, it's a shame it cannot be made more powerful by Smartbear.
Allow SoapUI assertions to vary depending on selected environment
In cases where API responses vary depending on environment and this is not in control of the QA team it would be useful to be able to specify which environments an assertion applies to. This would allow a test step to have different assertions only a subset of which are evaluated in any given environment.
Smart Assertion Conditions NOT Matches Regex
List of Smart Assertion Conditions 0. <, > , >= , <= 1. Equals AND Not Equal 3. Equals (one of) AND Not Equal (one of) 5. Exists AND Does NOT Exist 7. Empty AND NOT Empty 9. Contains AND does NOT Contain 11. Matches (regex) AND.... AND..... (!!) And... and..... and....!!! Uh..... what happened to NOT MATCHES (regex) ?!?!
Update Custom Property references in "Run Test Case" values, if Custom Property is renamed
It would be great, if ReadyAPI/SoapUI NG would update usages of custom properties in case of renaming the custom property, even if there are used in the value part of the property definiton of "Run Test Case" test steps. 1. Create TestSuite Repro - Custom Property MyRepro 2. Create TestCase Foo - Custom Property MyFoo 3. Create TestCase Bar 3a. Create TestStep "Run TestCase Foo" in TestCase "Bar" 3b. Assign to "MyFoo" the value value ${#TestSuite#MyRepro} 4. Rename the Custom Property "MyRepro" to "MyNewRepro" 5. Check the value in TestStep "Run TestCase Foo" -> Value is still "${#TestSuite#MyRepro}" and not "${#TestSuite#MyNewRepro}" If the custom property is used in a "Soap Request" test step, the usage is updated. So it would be a great help, if same happens in case of usages in "Run TestCase" test steps. With regardsRefreshing of the Reports without reopening the application
Hi All, I had earlier faced issues while generating a new report template in ReadyAPI wherein the report does not compile/load all the components unless and until i close & reopen the application. As Jasper Reports are integrated into ReadyAPI, the compilation must happen immediately instead of loading the plugins only at the time of startup. It would be good to see this feature in the next coming versions. Cheers, Sai Kiran,
Manage the projectVersion field in "Setting.xml" , so it doesn't update with every save or reload
Reference Issue -https://community.smartbear.com/t5/ReadyAPI-Questions/Ready-API-3-42-0-automatically-updates-projectVersion-every-time/m-p/240988/emcs_t/S2h8ZW1haWx8dG9waWNfc3Vic2NyaXB0aW9ufExBSklETVhHWkdEMTUxfDI0MDk4OHxTVUJTQ1JJUFRJT05TfGhL#M57307 projectVersion value changes everytime a project is saved. When trying to Pull changes from git, setting.xml needs to be committed first, but it re-appears again as a new change, which blocks pulling from git. The "Discard all changes", don't really discard the document.
