Bug 59851 - No unit test fixture marker for F# modules
Summary: No unit test fixture marker for F# modules
Status: NEW
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: F# Add-in (show other bugs)
Version: Trunk
Hardware: PC Mac OS
: Normal normal
Target Milestone: 15.6
Assignee: Jason Imison
URL:
Depends on:
Blocks:
 
Reported: 2017-09-29 14:46 UTC by Jason Imison
Modified: 2017-10-11 11:45 UTC (History)
3 users (show)

See Also:
Tags:
Is this bug a regression?: ---
Last known good build:


Attachments
No marker next to module (189.87 KB, image/png)
2017-09-29 14:46 UTC, Jason Imison
Details
Bug demo (611.92 KB, image/gif)
2017-10-06 09:02 UTC, Jason Imison
Details

Description Jason Imison 2017-09-29 14:46:27 UTC
Created attachment 25035 [details]
No marker next to module

See attachment. Types get a fixture marker, but modules do not.
Comment 1 Matt Ward 2017-10-02 08:36:00 UTC
This seems OK to work for me in VS Mac 7.3.0.639 (d15-5). Might be doing something wrong. The only problem I can see is that methods in the module are not shown in the Unit Tests window and if you run the tests for the project the module does not get marked green or red in the Unit Tests window and stays undefined.
Comment 2 Jason Imison 2017-10-06 09:02:17 UTC
Created attachment 25145 [details]
Bug demo

Just took another look at this and you can see the issue in the files TagComments.fs and TypeSignatureHelp.fs in the F# addin test project.

I didn't notice last time, but the marker _does_ appear but then promptly disappears again for some reason (see attachment)
Comment 3 Jason Imison 2017-10-06 09:04:52 UTC
Removing NEEDINFO
Comment 4 Mike Krüger 2017-10-10 11:08:32 UTC
Can't reproduce with master:

https://screencast.com/t/dVtCLWOkhq

Are you able to with the latest master ?
Comment 5 Jason Imison 2017-10-11 11:45:29 UTC
@Mike - I can still reproduce. I just realised that this issue only occurs when you using IExtendingTextLineMarkers. (Turn on "Show function type signatures" in F# settings)

Note You need to log in before you can comment on or make changes to this bug.