How to change configuration in Microsoft test manager 2015 when test suite is already executed and passed

Question

0.00/5 (No votes)

See more:

Test case is already executed and passed but with different configuration. In case want to change configuration of passed test case what can be done? I tried changing the configuration but that test case moved to 'Active' section from 'Passed' section. and all evidences are removed as it is moved to 'Active' state.
Please suggest solution if don't want to loose evidences.

What I have tried:

Test case is already executed and passed but with different configuration. In case want to change configuration of passed test case what can be done? I tried changing the configuration but that test case moved to 'Active' section from 'Passed' section. and all evidences are removed as it is moved to 'Active' state.

Posted 5-Jul-18 3:18am

Shail Mishra

Updated 5-Jul-18 22:23pm

Richard MacCutchan

v2

Add a Solution

Comments

Richard MacCutchan 5-Jul-18 9:30am

If you change the configuration then you most likely need to rerun the tests. Any previous data will no longer be valid.

Richard MacCutchan 6-Jul-18 4:26am

It does not matter how many times you edit this question the answer will remain the same. If you change the configuration then the previous results are no longer valid, so you must run the tests again with the new configuration settings.

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Dave Kreskowiak · Accepted Answer · 2018-07-05T04:17:00

Solution 1

Seriously? Did you even think about what you just said?

Changing the configuration of a test invalidates the results from the previous run of the test!

If you want a different configuration for the same test, create a copy of the test with the different configuration. Either that, or you have to write a test that calls another method that does the actual work, but can be called with different configurations.

BUT YOU SHOULD NOT DO THIS! This violates the rules of writing "simple, self contained" tests. Truthfully, based on what you've asked, I get the feeling you already violated this rule.

Posted 5-Jul-18 4:17am

Dave Kreskowiak

Comments

[no name] 6-Jul-18 2:58am

But rerunning the test case is not the correct solution. I forgot to select correct configuration and I executed it with default one. But that does not mean I have to rerun it and take all evidences again. It's really painful, as test case has many steps inside.
We need to have specific option to change configuration of already executed test cases which will just change configuration but will keep all evidences as it is.
Please suggest.

Dave Kreskowiak 6-Jul-18 9:10am

If by "configuration" you're talking about the difference between a Debug build and a Release build, I highly suggest you get that correct before you run the tests. Changing that automatically invalidates the results of all tests and with good reason. You just changed the behavior of all the code compiled by changing the configuration.

You have no options here. You either pick the correct configuration before you compile and run the tests, or you go back, pick the correct configuration and run them ALL again.