FsCheck.xUnit has incomplete source information in Visual Studio
See original GitHub issueI have a <Property> based test like the following
module Foo = [<Property>] let``Reverse of reverse of a list is the original list``(xs:list<int>) = List.rev(List.rev xs) = xs
The discovered test in Test Explorer isn’t having the appropriate Source code information. Clicking the test in the Test Explorer in visual studio gives the following in the pane where the source file name and line information is displayed.
Source: no source available.
Looks like when the test is discovered the xUnit is unable to set the “CodeFilePath” and “LineNumber” information in the TestCase object.
Issue Analytics
- State:
- Created 7 years ago
- Comments:9 (6 by maintainers)
Top Results From Across the Web
Convert a test in a properties based test in C# · Issue #137
I've created another branch with xunit < 2.0 for enabling FsCheck integration, fsc-xunit19. This is the direct link to altered source file, so ......
Read more >Properties throw off xUnit and the Test Explorer
It appears that test discovery fails silently if binding redirects are not set properly. This just cost me about 3 hours, so I...
Read more >Expecto Alternatives - Testing - Awesome .NET - LibHunt
A very extensive set of extension methods that allow you to more naturally specify the expected outcome of a TDD or BDD-style unit...
Read more >Sergey Tihon's Blog – Going its own way with F#
The F# compiler service now always looks at the actual C# sources, ... Your Voice Matters – Visual Studio Blog (microsoft.com) ... Have...
Read more >A fun community for developers to connect over code, tech ...
Hunting through the code line by line, I eventually find this. WHY IS THIS ALLOWED TO COMPILE · rant visual studio debug ·...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@tlycken, if it helps, I’ve made that mistake at least once within the last 6 months 😳 Took me some time to figure out, too…
Seems like this was solved or at least not reproducible.