2012년 5월 29일 화요일 오후 3:52
I created a bug from a test case I was running, and after the bug was marked as fixed I wanted to use the “Verify” feature in MTM 2010 (SP1 and FP2 installed) to test it so that I could update the bug. Alas, I received this lovely error - "You cannot run the selected tests. The test result no longer exists on the server". Between the time that I created the bug and went back to “Verify” it today, I had made some changes to my test suites, including deleting one, and was warned that I might lose access to test results. I am assuming that is the reason for the error as this test case was in that deleted suite.I think I understand what the issue is here from the tool's perspective, but really all I need as a tester are the repro steps to re-run the test. Those steps are in my bug via the original test case regardless of the existence of test results. Seems silly that I have no ability to just re-run the test at this point regardless of if the original results are available or not. Verify is greyed out but how about also giving me a re-Run option? Very disruptive to my flow to have to change views back to "Test | Run Tests" view, navigate to the test, and Run from there instead. But I digress, that's just a usability thing and maybe it is just me complaining about it. I will search Connect and see if it is there for MTM 11. On to my real issue.
I was figuring I could just manually create the link I needed between the new passed test result and the bug to prove it is fixed, but ran into this problem (see screenshot below).
The two test results displayed are from before when I originally created the bug. I want to attach a third result, the result that I just got by manually re-running that test linked to the bug, to verify/prove that the bug was closed. So I did just that, went to the result and tried to link it back to this work item. But when I go to the test result I want to link it to, I can’t create that link type ("Test Result"), ARGH. All it lets me select for relationship type is “related”, and when I return back to the bug, as in the screenshot above, this third passed test result DOES NOT appear in the “test result” link grouping. I only see the original 2. This is a problem. Is there a way to do what I am trying to do?
The above seems to be linking the Test CASE not the individual test RESULT. How can I link a test result to a bug after the fact?
- 편집됨 AngelaB 2012년 5월 29일 화요일 오후 3:53 more clarification
2012년 5월 30일 수요일 오전 9:26중재자
Thank you for your post.
1. For add link for a test result just see one link type-Related.
First, link types contain work item link types and external link types. Work item link types are for work items, the link mode likes work item--work item. External link types, the link mode likes work item--external resource, external resource--work item. But there is no link type that the link mode likes external resource--external resource.
Work item link types contain:
Test Case/Share Steps
Among them, Related link type is the only one that do not have direction, that do not need link form one work item to another work item, Related link could from one work item to external resource, external resource--work item.
External link types contain:
These kind of link types you can use in the drop down list when add link type object is a work item.
Both of above link types will exist when the object you want to add link is a work item.
But, you want add link to test result, test result is not a work item. First, External lin types won't list in the dropdown list. Second, the link type could not be work item link types like Affected By, Affects, Child, Parent those form work item to work item link types. "Relate" is the just one link type you can choose when the add link type object is external resource.
I hope above information could clear explain why the link types in the drop down list are different when add link to test result and bug.
2. For not see link relation between new test result and the fixed bug, i test it. It works as it is in my side. The setps i did were:
- Open the the new test result that generate fron i re-run the test.
- Expand Links in the test result, click Add.
- Select the only one link type "Related", query out the fixed bug, at last click OK.
- SAVE the test result. I am afraid you do not save the test result.
I hope this information will help resolve this issue.
If anything is unclear, please free feel to let me know.
Lily Wu [MSFT]
MSDN Community Support | Feedback to us
2012년 5월 31일 목요일 오후 2:21
I understand how links work, and that a test result is not a work item type, that was not my point, or my question. You did answer it in a round about way but I am still confused about something. It's seems to be an issue of the tooling, and the messages it provides, being a bit confusing in this scenario.
My questions was how do I create the type of external link I want between a test result and a bug through the UI. The MTM tooling, specifically TOLD ME - "To link a test result to the work item, you must open the test result and associate the work item with the test result" - but it's not terribly intuitive HOW to do it. I opened the test result, I did not see a way to ASSOCIATE that test RESULT with the bug through any of the available buttons. You said it yourself, you can only relate two work items and a test result is not a work item. My only option was to relate (not associate) the TEST CASE (not the test result) to the bug, which in my mind was NOT the same thing.
For the record, after this post was sent, I noticed the new test result now showing up in the bug's "Test Result" section of the "All Links" tab after I refreshed a few times. I wonder if that association between a test result and a bug is automatic, if the test work item and bug work item are related. And so then maybe association is not actually something I can set? If so, that message needs to be changed to stop implying that I can.
2012년 7월 31일 화요일 오후 8:06
Looking for validation that I am doing things correctly as per my last paragraph in that last post. The tooling provides messaging that is inconsistent and confusing to my new QA team who are all ramping up on MTM.