- Home /
- Team Services /
Get help from our community supported forum
Report an issue from
within Visual Studio*
This allows diagnostic information to be included in your report
1
Open Visual Studio
2
Select Report a Problem
3
Type and Submit
*Available only on Visual Studio 2017 Preview 3 and newer releases
VSTS - clicking View Tests link from test case invitation email returns "The test suite with id xxxx does not exist"
Steps to Reproduce:
1) Create a test plan and assign the test plan to a person to run (select option to send email).
2) Recipient of email is working on a test plan that is different from the one in #1.
3) When recipient receives the email, he/she clicks the View Tests link.
expected result: Display the test plan from #1 along with test cases that has been assigned.
actual result: Displays the test plan in #2 and error "The test suite with id xxxx does not exist."
User can get such an error in below two conditions:
1. The suite was deleted before the user clicked the email link, which is unlikely in this case.
2. The test plan is not in area path in the context of which the user is accessing Test hub. You can find which the area path that is being queried by clicking on the filter icon next to the test plan selection dropdown and set it to the right area path in which the target plan is present. Note that the test plan filter is set by default to the 'Team context' but it can be overridden by the user as well.
Thanks
Manoj
The test suite has not been deleted.
Also the test plan filter has only 1 criteria: Work Item Type in Group Microsoft.TestPlanCategory
Could there be other reasons?
The other reason could be permissions. User needs to have 'View test runs' permission at the team project level and 'View work items in this node' permission at the area path level in which the test plan and suite are present. TFS permissions are described here: https://www.visualstudio.com/en-us/docs/setup-admin/permissions
If the permissions are correct, please drop us a mail at devops_tools@microsoft.com and we will setup a session to debug the issue.
Thanks
Manoj
We have found the root cause for this issue and filed a bug to fix it. ETA for the fix is the next scheduled VSTS deployment which will be 3-6 weeks from now.
Thank you for your feedback! We have fixed the problem in an upcoming release. Thank you for helping us build a better Visual Studio!
Hi Judy, we have received your mail and will get in touch with you in the next few days. There has been a flurry of issues coming our way last week, and we are working though them. Thanks for your patience.
-Manoj
36 People are following this
