ContributionsMost RecentMost LikesSolutionsRe: Compare multiple values from database against API response If I understand the use case correctly, the DB call could be set as a JDBC Datasource that would have properties (columns) for each value you want to use either in a request or as part of the validation. The Datasource would split each record into a new row, so the input value and expected values are aligned in the assertion or other test steps that follow. In your requests, the Get Data menu can build a reference to the input value, while Get Data can also be used in assertions (either added via the outline view, or for something like a 'contains' assertion) This only really works when a single table/SQL returns all the values required - if it happens across multiple calls, the data would have to be organized as part of the test flow before being mapped to a datasource. Re: Problem with remote repo URL Hello! I tested this out and was unable to use a username/password combination to connect to an Azure repository like I would with Github or Bitbucket. Instead, using a GIT profile (not linked to a specific provider) in ReadyAPI that held my username & an Azure PAT I was able to drop in the remote URL as you have shown and successfully push to the remote Azure repository. Re: testrunner.bat command to disable a particular TestCase from a TestSuite Event scripting may be a good fit but does require enabling/disabling testcases, which in the case of an error or more granular runs could cause unexpected results. An alternative could be to use the TestCase tags that can be configured at a TestSuite level. These can be set within the TestSuite Editor and you could either tag the 'must run' cases, or 'optional' ones. Using testrunner.bat, one or many of these tags can be specified at run time using the -T argument along with operators for more complex conditionals. This will avoid enabling/disabling a testcase on the fly but should provide the flexibility required on what to run. These can also be used at a project level to tag specific testsuites that should share groupings. Re: Integrating SoapUI tests into SpecFlow Sounds like an interesting use case! It might be worth checking out our Swagger-Assert4J library, while it doesn't support the full ReadyAPI suite (which would be TestServer), it does have similar functionality to our open source SoapUI and provides an interface that might be a good fit for your project.