VS2022 V17.4.5 problem
I have seen some issues with the Test Explorer pane on VS2022 with Specflow V2022.1.91.26832 since I upgraded Visual Studio to V17.4.5.
- The icon on the Test Explorer tree view node stopped showing the status of the test . The icon remains to show the exclamation point and never changes when the test runs.
- Double-clicking the tree view node does not open the Specflow file.
- Test Detail Summary at the bottom of the Test Explorer pane does not show any information such as where it fails and how.
They just worked fine with Visual Studio to V17.4.4. So, I think Microsoft broke Specflow in the latest build somehow.
Has anyone else noticed the issues?
Tetsu
-
Seeing this as well. There are errors on the test output pain related to unable to find - vstestadapter
Log level is set to Informational (Default).
Connected to test environment '< Local Windows Environment >'
Source code repository not available. Some features may not work as expected.
Test data store opened in 0.209 sec.
========== Starting test discovery ==========
========== Test discovery skipped: All test containers are up to date ==========
System.Collections.Generic.KeyNotFoundException: Unable to find UniqueTest VSTestAdapter,C:\ADO\Tests\bin\Debug\Tests.dll,Tests.AutomatedEmails.#::TestAssembly:Tests/Feature:AutomatedEmails/Scenario:Verify..testname
at Microsoft.VisualStudio.TestStorage.TestStoreHierarchyNode.LookupUniqueTest(MergedTestIndex index)
at Microsoft.VisualStudio.TestStorage.TestStoreHierarchyIndex.<>c__DisplayClass50_0.<GetUniqueTestsForNodes>b__0(TestStoreHierarchyNode ct)
at System.Linq.Enumerable.WhereSelectEnumerableIterator`2.MoveNext()
at Microsoft.VisualStudio.TestStorage.TestStore.<GetTestDetailsForNodes>d__132.MoveNext()
at System.Collections.Generic.List`1..ctor(IEnumerable`1 collection)
at System.Linq.Enumerable.ToList[TSource](IEnumerable`1 source)
at Microsoft.VisualStudio.TestWindow.Host.TestWindowStoreService.<>c__DisplayClass50_0.<QueryTestDetailAsync>b__0()
at Microsoft.VisualStudio.TestWindow.Logging.ILoggerExtensions.<CallWithCatchAsync>d__11`1.MoveNext()
System.Collections.Generic.KeyNotFoundException: Unable to find UniqueTest VSTestAdapter,C:\ADO\Tests\bin\Debug\Tests.dll,Tests.AutomatedEmails.#::TestAssembly:Tests
at Microsoft.VisualStudio.TestStorage.TestStoreHierarchyNode.LookupUniqueTest(MergedTestIndex index)
at Microsoft.VisualStudio.TestStorage.TestStoreHierarchyIndex.<>c__DisplayClass50_0.<GetUniqueTestsForNodes>b__0(TestStoreHierarchyNode ct)
at System.Linq.Enumerable.WhereSelectEnumerableIterator`2.MoveNext()
at Microsoft.VisualStudio.TestStorage.TestStore.<GetTestDetailsForNodes>d__132.MoveNext()
at System.Collections.Generic.List`1..ctor(IEnumerable`1 collection)
at System.Linq.Enumerable.ToList[TSource](IEnumerable`1 source)
at Microsoft.VisualStudio.TestWindow.Host.TestWindowStoreService.<>c__DisplayClass50_0.<QueryTestDetailAsync>b__0()
at Microsoft.VisualStudio.TestWindow.Logging.ILoggerExtensions.<CallWithCatchAsync>d__11`1.MoveNext()0 -
I'm having the same issue here. Tests run and pass or fail, the report is generated but Visual Studio is not showing the results as expected. I think I'll need to downgrade.
0 -
I have the same issue. Is Specflow working on a fix?
0 -
This issue appears to be fixed in VS 2022 V17.5.4.
1 -
Thank you Tetsuo Shimizu for the notification! The issue my team was having on V17.4.5 was resolved when we updated to V17.5.4.
0
Please sign in to leave a comment.
Comments
5 comments