I suggest you ...

Allow testers to edit test cases inside Manual Test Runner

After a test has been loaded into Test Runner, I often find that I have to make some changes to the test case while running it (some build changes, some corner cases etc). It is painful to switch back and forth between MTM (to edit test cases) and Test Runner (to run tests).

241 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    I agree to the terms of service
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Shankar SathiamurthiShankar Sathiamurthi shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    3 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      Submitting...
      • Dan GawareckiDan Gawarecki commented  ·   ·  Flag as inappropriate

        Answer is "Yes" to proposed constraint by"Anu MSFT" (on 7/26/2011).

        Note that HP's "Quality Center" has had this capability for *years*. I was aghast when I found out MTM lacked this very basic feature- who writes a perfect test case the first time? There's often such a long time lag between writing the initial test case and executing it, that software has changed enough that test case must be updated to be truly useful.

      • BertrandHBertrandH commented  ·   ·  Flag as inappropriate

        @anu
        In some instances you want to update the expected results of the test case (the test step is a pass or failure). It would be nice if those changes could be persisted with my current test run and not only be available for the next time.
        From an auditing perspective (not sure this is very important though, it is not for me) could'nt there is a mix up on what the testers indicate as a pass/fail (the old value) and what he meant (the new value that he entered while editing during the run).

      • Anu MSFTAnu MSFT commented  ·   ·  Flag as inappropriate

        If we were to implement this with a constraint that you won't be able to use the changes immediately in the same test run but can edit and save these changes for future runs, would that be an acceptable solution?

      Feedback and Knowledge Base