WIth metals, I'm using sbt as my build server in an (experimental :-/) multi project setup,
I want to customise some integration tests
class WithDbFramework extends utest.runner.Framework
In an SBT terminal, the tests run fine.
If I click on the "ghost link" to run the test "in place" in metals, I get errors. The test looks for a test config file;
val confFile = new File("./modules/backend/src/test/scala/dev.conf")
which apparently, it can't find ...
[ERROR] Uncaught exception when running tests: org.ekrich.config.ConfigException$Missing: ./modules/backend/src/test/scala/dev.conf (not found): No configuration setting found for key 'db'
Would this be expected? Is it expected that an sbt terminal exhibits different behaviour to "metals runner"?
script.sc, suggestions should work fine? :o
script.scin an empty directory Metals will assume that you have an ammonite script and will prompt you to import it
fallbackScalaVersionin your settings
// ammonite <version>