Rider Support?

[varon]

Jetbrains has had the issue outstanding for 2 years now. https://youtrack.jetbrains.com/issue/RIDER-7172

Is there anything we can do on expecto's side to get stuff to work?

[drhumlen]

2nd. Would be very nice to have! Much needed, especially since Rider doesn't understand that let main argv is the last declaration in the compilation sequence:

[auduchinok]

@varon We've started working on adding Expecto support to Rider. It currently seems nothing needs to be added or changed in Expecto itself to get some initial tests running/debugging.

[varon]

GLORIOUS

[drhumlen]

@auduchinok : It may be a lot to ask, but will it also allow us to see coverage? That could be very useful

[auduchinok]

@drhumlen There're chances it will be able to get it (almost?) for free the same way we didn't have to do anything to get coverage working in F#. If it only requires implementing some simple Expecto-specific components then it'll be easy to address. We'll see. :)

[drhumlen]

@auduchinok. Cool! :) Do you have any ETA? (I'm using EAPs whenever available)

[auduchinok]

@drhumlen No estimates to share for now.

If you want some status updates, here're a test session results for the Expecto dotnet template, after run/debug:

Now it needs more work in the discovery part.

[ErikSchierboom]

Any progress on getting expecto integrated into Rider? Really love both :)

[auduchinok]

@ErikSchierboom Yes, most of pre-requirements on F# plugin side are ready. We need to finish integration of inner tests discovery and some other things. It's likely it all can come to 2020.1 EAP, though, no particular promises for now, since it also needs changes in Rider itself. :)

[ErikSchierboom]

Great! Looking forward to it.

[drhumlen]

I'm suspecting that it's really hard for Rider to pinpoint the location of a test since Expecto by design is all about programmable flexible testing. With the other libraries, modules and their [<Fact>]-let bindings are unambiguously placed, but with expecto it can be anywhere.

If it doesn't make sense to add Expecto support to Riderr, that's ok. There are other more low-hanging fruits I'd rather have I think. 🤔

[auduchinok]

@fc1943s Sorry for no updates. We didn't move much forward during 2020.1 development cycle.
Some of the changes on F# support side depend on a unit test infrastructure refactoring and it was postponed till 2020.2 AFAIK. I'm going to try working it around so in the worst case we could enable at least a limited support in 2020.2 if the unit tests refactoring is not done by that time.

[varon]

Thanks for the update @auduchinok. Really looking forward to this!