ContributionsMost RecentMost LikesSolutionsRe: Bulk editing tests and requests I've had a bit more of a look at this. Using a find across files (VS Code) the only place I see that I can edit my assetname value would be in the request in the test case itself. Filenames (for excel data source) I cannot edit in bulk. Test names themselves (corresponding to assetname) cannot be edited. XML filenames of tests would need to be manually changed. Re: Bulk editing tests and requests Thanks - yes, running a composite file. Tests are named in a fashion like: test 1 assetname1 test 2 assetname1 someothertest anotherassetname andanothertest anotherassetname In each of those the particular assetname would form part of the request. There is also an edit needed to each time a Data Source step is used, as it would also be pointed at something like assetname1.xlsx etc. The creation of those xlsx files isn't an issue in this case. I used SoapUI in the past and recall having to do this kind of editing in the XML too. Bulk editing tests and requests I have a large test suite which needs to update in relation to the application api test data. I'd like to bulk edit (find and replace type edit) where a particular test case has a given string in name (an asset name) and the corresponding request. Is there a means to do this across a test suite? SolvedRe: Adding a default argument to requests the redirect request is a query parameter. the format parameter can have no value, JSON, or XML. No value is a default to JSON. Is the redirect then also possible to be setup as a custom project level property? All tests were built in ReadyAPI from our imported swagger json. Re: Adding a default argument to requests Yes - we can request Application/JSON or XML for an example of a GET to a Resource - /rest/data/beta/ourendpoint/views and currently using parameters to send up the redirect (this was to test using specifically we can redirect via a parameter. in the call) ?$format=&$streamRedirectOptIn where we specifically want the XML format and redirect, that parameter becomes ?$format=XML&$streamRedirectOptIn that's what we need to send up to use the optional format and the optional redirect. Currently, I'm setting that?$format=&$streamRedirectOptIn in that format parameter, against each test. I'd just like to have a project level parameter that I can apply. Re: Adding a default argument to requests Yes - so - in the test request to our particular endpoint, there is a parameter $format which specifies response type. Default response type is JSON. This is optional to send in the $format request, but it is required when adding the additional redirect portion to the $format string - e.g. JSON&$redirect Adding a default argument to requests We are currently using a parameter $format. The default is to specify returning JSON. This can be left empty. If we want to add a notification to server to use a redirect, we have to add this to the $format parameter, but specifically after the JSON entry, which must be placed at start of string. Is it possible to : create a parameter at a project level which can be applied to all requests can this be selected to use/not use as desired SolvedRe: Excel data source read by column Not sure that answers where Jars or DLLS should go - into each project level folder that uses them? If so, just under that level? Re: Excel data sources - using a relative path name for files When I try to use the $projectDir variable, I get errors on my datasource test steps: Excel data sources - using a relative path name for files We need to use ReadyAPI across different machines. Our code is checked out from Git and sometimes our local directories differ (for example I use E:\, a colleague uses C:\) As we need to share our data sources (excel files) that are also checked in, how can they be set in ReadyAPI to use a relative Path, instead of fixed paths? Solved