E.g.
This happens because the extension gets a flat list of tests (names concatenated with slashes) from the external test runner, and therefore can't tell the different between a real slash that was inserted to indicate hierarchy, and a slash that's actually just part of the tests's name. See: /MonoDevelop.UnitTesting.Expecto/ExpectoTestSuites.fs#L251
Possible solutions:
- Escape slashes in test names in the external test runner (this feels a little dirty but would work)
- Send the tests back to the client in a tree form (can't use the actual
Expecto.Test since this isn't serializable, so we'd have to define our own Test tree type that mirrors it, but without the Expecto.TestCode)
- Change
FlatTestInfo.name to be name: string list instead of name: string, where each element is the hierarchy. (Of course code will have to be changed in the test runner to create the correct structure)
E.g.
This happens because the extension gets a flat list of tests (names concatenated with slashes) from the external test runner, and therefore can't tell the different between a real slash that was inserted to indicate hierarchy, and a slash that's actually just part of the tests's name. See: /MonoDevelop.UnitTesting.Expecto/ExpectoTestSuites.fs#L251
Possible solutions:
Expecto.Testsince this isn't serializable, so we'd have to define our own Test tree type that mirrors it, but without theExpecto.TestCode)FlatTestInfo.nameto bename: string listinstead ofname: string, where each element is the hierarchy. (Of course code will have to be changed in the test runner to create the correct structure)