{"id":5203,"date":"2012-04-10T22:34:00","date_gmt":"2012-04-10T22:34:00","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/visualstudioalm\/2012\/04\/10\/automatic-requirement-traceability-with-exploratory-testing\/"},"modified":"2022-07-26T03:10:39","modified_gmt":"2022-07-26T11:10:39","slug":"automatic-requirement-traceability-with-exploratory-testing","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/devops\/automatic-requirement-traceability-with-exploratory-testing\/","title":{"rendered":"Automatic requirement traceability with Exploratory Testing"},"content":{"rendered":"<p style=\"margin: 0in 0in 0pt;text-align: justify\">\n  <span style=\"font-family: 'Segoe UI Light','sans-serif';font-size: 11pt\">My favorite feature of <a href=\"http:\/\/msdn.microsoft.com\/en-us\/library\/hh191621(v=VS.110).aspx\">exploratory testing with Microsoft Test Manager<\/a> is automatic requirement traceability, that it automatically builds up my test plan as I perform my explorations. <\/span>\n<\/p>\n<p style=\"text-align: justify\">\n  <span style=\"font-family: 'Segoe UI Light','sans-serif';font-size: 11pt\">So let&#8217;s say that I have a backlog item that my team is working on and it is now ready to be tested. To perform exploratory testing on it, I launch Microsoft Test Manager and create a new empty test plan. This is how my Plan->Contents tab looks currently:<\/span>\n<\/p>\n<p style=\"text-align: justify\">\n  <span style=\"font-family: 'Segoe UI Light','sans-serif';font-size: 11pt\"><a href=\"https:\/\/devblogs.microsoft.com\/devops\/wp-content\/uploads\/sites\/6\/2012\/04\/7462.pic1_.png\"><img decoding=\"async\" alt=\"\" src=\"https:\/\/devblogs.microsoft.com\/devops\/wp-content\/uploads\/sites\/6\/2012\/04\/7462.pic1_.png\" border=\"0\" \/><\/a><\/span>\n<\/p>\n<p style=\"text-align: justify\">\n  <span style=\"font-family: 'Segoe UI Light','sans-serif';font-size: 11pt\"><\/span><span style=\"font-family: 'Segoe UI Light','sans-serif';font-size: 11pt\"><\/span>\u00a0\n<\/p>\n<p style=\"margin: 0in 0in 0pt;text-align: justify\">\n  <span style=\"font-family: 'Segoe UI Light','sans-serif';font-size: 11pt\">Now I select the relevant backlog item and start exploring it, similar to the walkthrough <a href=\"http:\/\/blogs.msdn.com\/b\/visualstudioalm\/archive\/2012\/03\/12\/getting-started-with-exploratory-testing.aspx\">here<\/a>. I launch my application, perform actions on it, take screenshots, add comments, create bugs and create test cases. I keep doing this for a while until I am confident that I have covered all the items in the acceptance criteria of the backlog item. After a few minutes of testing, this is how my exploratory testing window looks, I have created\u00a03 bugs and 5 test cases overall.<\/span>\n<\/p>\n<p style=\"margin: 0in 0in 0pt;text-align: justify\">\n  <span style=\"font-family: 'Segoe UI Light','sans-serif';font-size: 11pt\"><a href=\"https:\/\/devblogs.microsoft.com\/devops\/wp-content\/uploads\/sites\/6\/2012\/04\/6712.pic2_.png\"><img decoding=\"async\" alt=\"\" src=\"https:\/\/devblogs.microsoft.com\/devops\/wp-content\/uploads\/sites\/6\/2012\/04\/6712.pic2_.png\" border=\"0\" \/><\/a><\/span>\n<\/p>\n<p style=\"text-align: justify\">\n  <span style=\"font-family: 'Segoe UI Light','sans-serif';font-size: 11pt\"><\/span>\u00a0\n<\/p>\n<p style=\"margin: 0in 0in 0pt;text-align: justify\">\n  <span style=\"font-family: 'Segoe UI Light','sans-serif';font-size: 11pt\">Confident that I have covered everything, I click on &#8216;End testing&#8217; which takes me back to Test Manager. Here, after viewing the summary of my exploratory test session, I go back to my test<br \/>plan, which was completely blank when we had started. This is how it looks now:<\/span>\n<\/p>\n<p style=\"margin: 0in 0in 0pt;text-align: justify\">\n  <span style=\"font-family: 'Segoe UI Light','sans-serif';font-size: 11pt\"><\/span>\n<\/p>\n<p style=\"margin: 0in 0in 0pt;text-align: justify\">\n  <span style=\"font-family: 'Segoe UI Light','sans-serif';font-size: 11pt\"><a href=\"https:\/\/devblogs.microsoft.com\/devops\/wp-content\/uploads\/sites\/6\/2012\/04\/1411.pic3_.png\"><img decoding=\"async\" alt=\"\" src=\"https:\/\/devblogs.microsoft.com\/devops\/wp-content\/uploads\/sites\/6\/2012\/04\/1411.pic3_.png\" border=\"0\" \/><\/a><\/span>\n<\/p>\n<p style=\"margin: 0in 0in 0pt;text-align: justify\">\n  <span style=\"font-family: 'Segoe UI Light','sans-serif';font-size: 11pt\"><\/span>\u00a0\n<\/p>\n<p style=\"margin: 0in 0in 0pt;text-align: justify\">\n  <span style=\"font-family: 'Segoe UI Light','sans-serif';font-size: 11pt\">So while I was exploring my application a requirement based suite has been added to my test plan, consisting of all test cases that I created during my exploratory session. This is like a set of regression tests that can be used for verifying this feature in future test passes. As I go on exploring requirement work items, new suites will keep on getting added to my plan. In fact, If I had done my exploratory testing without the context of any work item, my test cases would have still been added to my test plan&#8217;s root suite. <\/span>\n<\/p>\n<p style=\"margin: 0in 0in 0pt;text-align: justify\">\n  <span style=\"font-family: 'Calibri','sans-serif';font-size: 11pt\">\u00a0<\/span>\n<\/p>\n<p style=\"margin: 0in 0in 0pt;text-align: justify\">\n  <span style=\"font-family: 'Segoe UI Light','sans-serif';font-size: 11pt\"><span style=\"font-family: 'Segoe UI Light','sans-serif';font-size: 11pt\">This saves me a lot of effort of writing test cases and then organizing them into a plan, since my test plan gets automatically built up while I perform my testing<\/span><\/span>.<span style=\"font-family: 'Segoe UI Light','sans-serif';font-size: 11pt\"><\/span><\/p>\n","protected":false},"excerpt":{"rendered":"<p>My favorite feature of exploratory testing with Microsoft Test Manager is automatic requirement traceability, that it automatically builds up my test plan as I perform my explorations. So let&#8217;s say that I have a backlog item that my team is working on and it is now ready to be tested. To perform exploratory testing on [&hellip;]<\/p>\n","protected":false},"author":87,"featured_media":45953,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[],"class_list":["post-5203","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-devops"],"acf":[],"blog_post_summary":"<p>My favorite feature of exploratory testing with Microsoft Test Manager is automatic requirement traceability, that it automatically builds up my test plan as I perform my explorations. So let&#8217;s say that I have a backlog item that my team is working on and it is now ready to be tested. To perform exploratory testing on [&hellip;]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/posts\/5203","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/users\/87"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/comments?post=5203"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/posts\/5203\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/media\/45953"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/media?parent=5203"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/categories?post=5203"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/tags?post=5203"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}