1. The Unit Test check-in policy cannot be used on team projects with multiple solutions.
Details: When multiple Visual Studio solutions are associated with the same team project, setting a Unit Test check-in policy for that team project will cause check-ins to fail.
Workaround: Do not set a Unit Test check-in policy for a team project that has more than one Visual Studio solutions associated with it.
2. Editing the link to an unpublished test causes the bug form to throw an exception.
Details: When you change the link to test results from the bug form, the bug form throws an exception if the test results have not been published.
Workaround: If you receive this exception, remove the invalid link from the bug form. To avoid this exception, publish the results before creating the bug or do not change the link.
3. Coverage Analysis Service is writing an event log warning when a build is deleted.
Details: Deleting a build that has tests published against it will cause the Coverage Analysis Service to write an event log warning.
Workaround: Ignore the event log warning.
4. Unable to publish test results when the client is logged in as a local user not recognized by Team Foundation Server.
Details: Trying to publish test results when the Visual Studio user is not recognized by Team Foundation Server will fail, even though Team Foundation Server does not ask you for valid credentials when it tries to publish test results.
Workaround: Run Visual Studio as a user recognized by Team Foundation Server.
1 comment:
Hello Friend! I just came across your blog and wanted to
drop you a note telling you how impressed I was with
the information you have posted here.
Keep up the great work, you are providing a great resource on the Internet here!
If you have a moment, please make a visit to my x10 wireless technology site.
Good luck in your endeavors!
Post a Comment