tests/elm.json still required for ALE to lint test files

[altaurog]

I gather that test-dependencies has been added to elm.json (formerly elm-package.json) to separate test dependencies. This does indeed seem to be a better approach than maintaining tests/elm.json separately.

However, when using vim/ALE, I see import errors. ALE runs elm make under the hood. It looks to me like it is essentially:

$ elm make --output=/dev/null tests/Example.elm

Which produces the following error

-- UNKNOWN IMPORT -------------------------------------------- tests/Example.elm

The Example module has a bad import:

    import Test

I cannot find that module! Is there a typo in the module name?

The "source-directories" field of your elm.json tells me to look in directories
like src, but it is not in any of them. Maybe it is in a package that is not
installed yet?

Of course, elm-explorations/test is in test-dependencies, not dependencies.

By creating tests/elm.json with adjusted source-directories and dependencies, I can get the make command (and thereby ALE) to work. But this confuses elm-test and it fails with the following:

Error: /path/to/my/project/tests/tests does not exist. Please create a tests/ directory in your project root!

As a quick and dirty workaround, I have a bash function as follows:

elmtest() {
    mv tests/elm.json tests/elmjson
    elm-test "$@"
    mv tests/elmjson tests/elm.json
}

But this is obviously not the right solution.
Is there a (better) way to do this now?

[avh4]

I believe you can do elm test make --output=/dev/null tests/Example.elm (note this is elm test make, not elm make) to build files that use the test dependencies.

[altaurog]

@avh4 thanks for the suggestion! With elm 0.19.0 elm test only gives an error, but elm-test make seems to do the trick. Is that documented somewhere? It isn’t in the usage help I get with elm-test --help.