Do you put tests outside the `tests/` folder?

[harrysarson]

EEK.

Could you file an issue (ideally with a SSCCE)? I am sorry we broke this for you

[Chadtech]

Oh great! Nice job figuring all this out @lydell !

Yes, on my two computers I have 0.19.1-revision2

[lydell]

Thanks! Though I’m not sure we want to be bring the “old” behavior back.

In all test runners I’ve ever used, running cool-test-runner path/to/some.file only runs the tests in that file, which is nice when debugging a failing tests for a certain module. If we also run tests in files that are imported that command could run a lot more tests than one would expect.

I have just looked at this quickly, but the impression I got from the PRs/issues leading up to the revision3 release was that 0.19.1 and 0.19.1-revision2 were regressions from 0.18 – the run tests via imports (if that’s even how it works, I haven’t dug into it) was an accident and never how it was supposed to work.

I need to dig deeper to know for sure, though.

[bdukes]

On Windows here, running elm-test Website/DesktopModules/ClientName/**/Tests/**/*.elm (via Gulp). Running just yarn elm-test --fuzz 100 --seed 213841382551479 Website/DesktopModules/Beekley/**/Tests/**/*.elm went from ~3.3 seconds to ~1.8 seconds with your fork (all tests found).

We use both IntelliJ and VS Code editors, and do get support from the editors for tests (though there is an extra config file needed for the IntellliJ plugin)

[lydell]

@bdukes Thanks, that’s great to hear! One question: The glob you use seem to match multiple directories, but IntelliJ only allows configuring one custom tests location? So what does your IntelliJ configuration look like?

[bdukes]

Yeah, I just point it to the root of that glob:

{
	"test-directory": "Website/DesktopModules/ClientName"
}

[grigorious]

1. I use VSC with elmtooling.elm-ls-vscode
2. The imports (Expect / Fuzz / Test) are marked as errors with red underlines
3. The imprts are in "test-dependencies"