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, ...
Add password parameter for the loadtestrunner
Hello, I'm using the latest version from RedayAPI (3.0.0) and my project is password protected - the properties are encrypted. When I want to run functional tests in pipeline, I can give the password over the command-line parameter -p but this parameter doesn't exists for the loadtestrunner. This fact is not an error but a missing function. Without this feature, encoding the properties in a project is a major drawback when you want to automate the load test because I must deactivate the passwort protection to run the loadtestrunner. This is a strong security restriction, especially if you want to protect the passwords/token/secrets used in cloud repositories. A lot of services are provided in the cload nowadays and the trend is increasing, besides the reason I ask the reader to vote for the function to introduce the password parameter for the loadtestrunner as well. Thanks in advance for the votes. Greetings, GiovanniAllow user to set logging level for maven-plugin via project configuration file
currently, when running the readyApi maven plugin, the logging level is set to info. We need a mechanism to set it to error or warning because the excessive logging is crashing our build slave. This could be done in the plugin configuration section of the pom.xml. Or the maven plugin could respect the user's log4j configuration files.
Default environment usable as an actual environment
Hello, in one of the recent versions we pretty much lost the ability to use the "default environment" as a real environment. It was even renamed to "no environment". I've used it as the "development" one and I was creating extra one for the higher - "test" environment. Now the default environment can't be really used to set up authorization to given endpoints for our APIs. I can't even copy it as a template for a new environment, meaning i have to create a new one from the scratch. Having to do that in multiple projects with plenty of API's and custom properties means huge extra time commitment to manage projects in our company's department. Can you please unlock the ability to clone this default environment and set authorization /proxy for the APIs? Thank you, JohnOptimizing all lists in test steps
For all my projects I need to add a lot of parameters. I've setup a compare Loop with a few elements that requires linking those parameters manually with other steps. In these steps the list is unsorted whereas this makes it a long term action to link each of them to the right parameter of the next step. e.g. 1) Groovy Script to fetch the file 2) DataSource to fetch some parameters (or all parameters) from that file for each childnode 3) Property Transfer that will link from Source to Target ==> when selecting the Property from Source you have a sorted list as was created in the "Transfers" section left. When selecting the target, the properties are unsorted regardless wether you've put it in a specific order in the REST Request or not. If you have a long list, this is awashmash of properties. It would be great if all lists that are visible and usable in ReadyAPI will show a sorted list as was created. Thanks in advance.
