MTM test run not updated in all sets

I assigned one test case to two different user stories. I know that this is not the cleanest method, but it helps if I created it.

In terms of testing, I added requirements and, therefore, their respective test cases. Now this single test case is present in two different test suites, as it tests two different user stories.

When I run this test case, I expect it to either fail or succeed in both sets, but it seems that there are two completely different instances of this test case in the plan, and I may have one pass and the other fail.

Is there a need for such behavior or is it unexpected, therefore, an error in MTM?

+4
source share
1 answer

When you create test plans for MTM, you can specify configurations for it and which one will be the default. Therefore, when you add new requirements, they automatically accept the default configuration. However, you can always change it by assigning another available configuration for any necessary requirements. My point is that the test script, owned by two different User Stories, when assigned to the test plan, contains additional information, which is the configuration that it will use to validate it.

So, if your test case A is assigned to user stories A and B, and these requirements were assigned to the same test plan , but they have different configurations, it is very possible that one test case is an instance for failure and the other is.

+2
source

Source: https://habr.com/ru/post/1387037/


All Articles