My QA team has been using MTM for only a few months, and we've already created a fairly robust repository of Shared Test Steps. These have proved to be very valuable and have helped with overall efficiency. In some instances, some of my team members are a bit ambivalent to create any seemingly redundant Test Cases. For example, Using 2 different Client Applications to test a specific error handling process in a BPM tool, could mandate 2 separate Test Case Work Items, with different initial set-up or pre-condition steps, however, the originating Client Application that creates the transaction, wouldn't necessarily affect the error handling process in the BPM tool...
So ideally, I'd like to be able to create 2 separate "Shared Steps" (One per originating application), and configure the Test at run time to allow alternate paths, without reporting any failed steps.
Sorry if this isn't crystal clear... Anyone have any ideas/solutions for this? Or know if there's an updated version of MTM with an Alternate Steps feature?
Thanks,
Jon