Test Management 2.0 Functionality

[Tamara12]

Hi everyone, 

I've been trying to configure Test Management 2.0 to use it for various UAT/ Regression testing coming up. I had a couple of questions that I haven't been able to find answers to on the SN website, and thought I would post here. Thank you in advance for any information you can pass my way 🙂 

My questions: 

1. Does each test need to have a verification step within it to run? What do these verification steps generally look like? 

2. Test Management 1.0 had an 'Overview' tab that provided reports on the progress of testing - is that functionality available in 2.0? 

3. Similarly as above, Test Management 1.0 allowed you to link incidents to failed tests - is this possible in 2.0? (given we are not utilizing the agile testing portion) 

Thank you! 

[Frank67 · Accepted solution]

1. Yes.  It just means that step gets the option of a Pass/Fail/Blocked outcome to which you can add comments and attachments (OOTB, only can add attachments if Fail or Blocked). No verification, it's just a line on the screen on which you can't comment or add any kind of outcome.  You may choose to only make the last step verified, for example you might like to write the last step as an expected outcome (eg user can log in successfully) and hang all your pass/fail/blocked info and comments off that, or all steps - depends how much detail you want to add where.

2. Don't compare TM1 to TM2, you'll only ever be disappointed!  But try the Test Board, this gives you a visual overview of progress (overall, pass, fail) on test plans only. If your tests aren't in a test execution suite in a test cycle on a plan, they might be in a test execution suite on its own. In which case you can also add the test execution suite related list on whatever you're testing (can add to project, enhancement, problem, release etc), and add the columns for percent (passed, failed, overall) which gives you a  nice bar view of completion on that individual execution suite. Caveat being that both only show percent for the tests that have been added to the execution suite - if it's only got one test and that passed, then it will look great until you add another twenty.

3. You can't link a test result to anything except the test, test run, and by proxy the test execution suite. Highly frustrating for many as it seems so logical that you should be able to link it to a defect. You should however be able to link the execution suite the test and its result both sit within, to an incident or problem or anything else, as they all use the task table.

[Tamara12]

Thank you Frank! This was really helpful.