Tests should group hierarchically in IDE

[jwosty]

I could have sworn this used to work some time in the past, but Expecto tests are not grouping into the appropriate hierarchy. I am on Windows 11 using JetBrains Rider 2024.3.4 and .NET 9.0.101 (with projects targeting .NET 8).

Screenshots for reference:

Expecto suite:

namespace ExpectoTestSuite
open Expecto
module Tests =
    [<Tests>]
    let tests =
        testList "Root" [
            testList "List1" [
                testCase "my test case 1" (fun () -> ())
                testCase "my test case 2" (fun () -> ())
            ]
            testList "List2" [
                testCase "my test case 1" (fun () -> ())
                testCase "my test case 2" (fun () -> ())
            ]
        ]
    

Xunit suite:

namespace MyNamespace

module MyModule1 =
    open System
    open Xunit

    [<Fact>]
    let ``My test 1`` () =
        Assert.True(true)
        
    [<Fact>]
    let ``My test 2`` () =
        Assert.True(true)
        
        
module MyModule2 =
    open System
    open Xunit

    [<Fact>]
    let ``My test 1`` () =
        Assert.True(true)
        
    [<Fact>]
    let ``My test 2`` () =
        Assert.True(true)
    

[Alxandr]

Just a heads-up, I am probably not going to work on this. I don't use rider, nor am I doing F# these days. I can review PRs and manage releases though, so if you would like to figure this out on your own be my guest :)

[jwosty]

@Alxandr

Just a heads-up, I am probably not going to work on this. I don't use rider, nor am I doing F# these days. I can review PRs and manage releases though, so if you would like to figure this out on your own be my guest :)

That's fine, just wanted to at least document it. (sad to hear you're no longer doing F# :( )

Does it work in Visual Studio or is this just a Rider thing?

Can't promise anything but maybe I'll find the time to take a look at it if it's not too complex

[jwosty]

Following up to confirm that it does indeed work in Visual Studio 2022 (I do have it installed on this machine after all).... Interesting. I wonder whether or not this is a Rider bug then.

How do you recommend to debug a local build of the plugin (to see if I can find something obvious)? I have no idea how this stuff works. If you are looking for someone else to pick up maintenance, a quick little document on that would go a long way. Or a pointer to existing documentation if there is any.

[Alxandr]

It's been so long since I had to debug a test-support library, that I can't say I remember exactly. I think the simple solution is to build the dll with Debugger.Break() built in, and then simply placing it in the bin directory of what you want to test. Writing logs to a well-known file-location is also a good technique for when you don't want to attach a debugger. This should be way simpler to do, as the justfile in the repository already has what you need to run dotnet test with a freshly built YoloDev.Expecto.TestSdk IIRC.