Add a Regular Expression pattern to a String Generator
Current state Currently, the String generator allows to specify the length of the string and the string contents by character categories: Letters – By default, this check box is selected. Digits – By default, this check box is selected. Spaces – By default, this check box is selected. Punctuation marks – By default, this check box is selected. The docs are here https://support.smartbear.com/readyapi/docs/testing/data-driven/types/generator/string.html . Proposal However, there are cases which need more precise string format. Regular expression would allow an elegant way to define the format. I suggest to add an option to set a regular expression pattern. The String generator would follow the regex pattern instead of string length and the above mentioned character categories.Randomly generated values in requests and other ReadyAPI functions
Current situation ReadyAPI DataGenerator provides different random values (random integer, email, name, city, etc.) I like this function since it creates nice test data. However, the random values are only accessible via DataGenerator DataSource. Proposal It would be great if we could use them in: REST, SOAP, and other requests Variable setup Groovy scripts etc. In ReadyAPI the random values could be available via: expansion e.g. ${#Random#FirstName} Get data function adding a Random category in the top level Implementation proposal Wrapping Java Faker (https://github.com/DiUS/java-faker ) would do the task. Java faker can be configured to use localized data (e.g. english names, spanish names, etc.) The faker provides a lot of interesting data useful for testing, just to name few of them: Address Animal App Artist Avatar Aviation Book Business Company Color File Finance Food Name Nation Number PhoneNumber and many more, including some funny categories like ChuckNorris.Delete multiple selected request headers at once [BUG?]
Current behaviour: 1) In the additional request headers tab of a SOAP/REST test step I select multiple headers (the selected headers visually are selected by having the color blue = OK). 2) I click on the delete bin button. 3) Only the first header is deleted. Expected behaviour: ALL of the selected headers should be deleted. If a use wants to delete 10 headers he now has to manually select them and delete them one-by-one. This is frustrating. Note: this issue has been around for ages. Additionally: We (luckily) can select and copy the headers properly by doing a select and then Ctrl+C. The feature of copy-pasting request headers might not be really visible in the UI (e.g. there is no "copy" button), but I am very grateful this is possible through Ctrl+C. Might be wise to visually allow this to?Allow 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.
Composite project oAuth data in separate file
When working on a composite project that has oAuth Auth. it comes to changes to the settings file (new tokens) while developing tests locally. So there is always a unwanted change to this file. Wouldn't it be nice if there is a separate file for just the data that can change in case of new token retrieval? The following can change (as far as I saw): accessToken; accessTokenIssuedTime; refreshToken I would add the separate file than to the git ignore, so that there is no change related to this anymore. It might be also an option to just store the tokens temporary?Re-insert the Assertion HTTP
in version 3.9.0 there is a smartAssertion created that deprecates the HTTP assertions. As all of my testcases (a huge amount) have this assertion I'm not going to adapt them manually as this will take a huge effort to do so. No clue why Smartbear has deleted this assertion as I think quasi all of the testers are using this!? Please, re-install the HTTP assertions!
