1

So basically, I'm using Visual Studio Online for some months, and I've a lot of existing test cases, each being associated with a unit test thanks to the Test Automation feature.

Since a few days, I cannot anymore associate test automation to my test cases. Might be related to the changes that have been introduced with the December 10th update: https://www.visualstudio.com/news/2015-dec-10-vso

Basically, all existing and new test cases now show an empty screen instead of the UI that allows me to specify which unit test is associated with the test case. Here's an screenshot from VS 2013:

enter image description here

Displaying the same UI from Test Manager also shows an empty UI:

enter image description here

The only way to display the fields associated to the test automation is now to use VSO:

enter image description here

The problem is, those fields are read only.

I've managed to modify my SCRUM process to slightly alter the Test Case work item type UI:

enter image description here

So now those fields are displayed here:

enter image description here

Those fields are not read only, but I do not have anymore the UI that allows to automatically fill them by choosing one of the unit test within the VS Solution.

So basically the question is: what's wrong with VSO, how can I use test automation again? Is this a bug/regression?

Similar (unanswered) question: https://social.msdn.microsoft.com/Forums/vstudio/en-US/6a09c3ac-168b-40ff-99f3-87955cf7e6ca/associated-automation-test-case-screen-is-blank?forum=TFService

Daniel Mann
  • 57,011
  • 13
  • 100
  • 120
ken2k
  • 48,145
  • 10
  • 116
  • 176
  • The same with this question: http://stackoverflow.com/questions/34360659/issue-linking-ranorex-codedui-tests-to-mtm-vso-2013-ci-following-recent-vso-upda – Eddie Chen - MSFT Dec 22 '15 at 00:54
  • @Eddie I wasn't able to find the other question, looks like it's really a regression of VSO... I'll try the suggestion you provided. Hopefully they'll fix this ASAP – ken2k Dec 22 '15 at 09:42

1 Answers1

2

This is a known issue that we introduced recently. We have a fix for it, and we will hotfix the service today or tomorrow.

Sorry for the inconvenience.

Ewald Hofman
  • 12,688
  • 3
  • 39
  • 44
  • What do we have to do to see it now? Update? Restart computer or Visual Studio? – philt5252 Dec 23 '15 at 15:45
  • 2
    We are working on servicing steps to update the cache, but if the issue is not resolved yet you can use one of these workarounds 1. Delete the local cache at C:\Users\{user}\AppData\Local\Microsoft\Team Foundation\{version} (make sure all instances of VS are closed) 2. Create a new field in any work item type using the admin process page After doing 1 or 2 hit refresh in VS and create a new test case. – Ewald Hofman Dec 23 '15 at 16:14