Currently we are able to associate only one mstest to a testcase in azure devops. I want to associate more than one test to a testcase. Any ideas please.
How to associate more tests to a testcase in azure devops
For this issue, I think it is not available to associate more than one test to a test case. A test can only be associated with one test case. For example: suppose we associate multiple tests into a test case. When running this test case, some of the tests successes and some of the tests failures, we can't determine whether the test case is successful or not, so this is unreasonable.
If you want to run multiple tests,you need to create multiple test cases.You can also try to create a test Plan or test suite, then add multiple test cases to the test suite or test plan, then run the test suite or test plan.
Please refer to Create test plans and test suites.
Related
How to create a duplicate test suite from an existing suite in azure DevOps.
Suite1
-suite1.1
-suite1.2
According to your description, currently there is no option to achieve this.
You can use the user interface to import a test suite from one test plan, within the same or different project, to another test plan in the current project. This action essentially copies or clones the test suite, creating a new test suite and duplicating any sub-test suites. The test cases referenced by the test suites are not duplicated, but referenced by the cloned test suites.
For more information, you could refer to this documentation.
I want to populate test plan with result of tests that are done by our CI pipeline on github. I am thinking of using a release pipeline like this. (Azure DevOps Test Plans - Synchronize JUnit test results in Runs with test cases on Tests Plan)
But as the author was not able to populate test plans with it. I am looking for a better solution.
As I need the project report for the test plan.
How to run testrigor tests on different environments like QA, Preprod? I need to data driven the environment specific urls
There are different ways to achieve that in testRigor.
Using different test suites, one per environment. One of the suites can contain the test cases and the others can be children of it inheriting the test cases.
On the same suite by using "branch testing". When you call testRigor via API you can trigger branch testing specifying with URL will be the target of the test. Detail of this can be found on CI/CD integration menu option within a test suite.
I will try to explain the setup the procedure and hopefully someone can tell me what is the best approach to achieve my question at the end.
Setup:
We have the following environments for our application: QA UAT and Prod.
QA is our internal test environment whereas UAT and Prod are on customer side.
Procedure:
We prepare test cases in DevOps, and then run tests in the QA environment.
If all is ok and we are ready for UAT, application is deployed to UAT in order to have a test session (UAT session) with the customer, The test session will run test cases which are a subset of the original test cases which were used during the QA phase
Similar is repeated for Prod. except that usually the customer is not involved.
Question:
What is the best practice to have these different test cases sets (QA, UAT and Prod), in order to keep a record of the test runs on each of the environments.
I can think of:
Creating 3 test plans which reference the main set?
or creating 3 test suites?
or creating 3 configurations?
Your help is appreciated.
P.S. Mostly we do manual testing
different sets of test cases for different environments in Azure DevOps
We recommend you create 3 test plan for different environments, for each environments, you can create a test plan and import the existing test cases into that plan. You can also, if you wish, divide the test cases into separate test suites within the plan to enable easier management and monitoring of these separate sets of test cases.
Note: If you copy or clone the test cases. A copy creates a new baseline. Changes to these new test cases don't affect your previous test plans.
I'm currently running xUnit unit tests in by build pipeline to prevent releasing builds with failing tests. I see that there's an option to associated automated tests with test plans within Azure DevOps. Is this a good practice for unit tests, or should this only be done with functional and/or integration tests?
Run unit, function and integration test suites in Azure Pipelines. Azure Test plans is supposed to improve overall code quality by using manual and exploratory testing services for your applications.