Ability to setup Env vars for running tests

Is this a bug report or a feature request?

🎁 Feature request

Version Info

N/A

How does one specify env vars for running tests? I have npm scripts setup to initialise env vars before running tests like these:

  ...
  "scripts": {
    "test": "better-npm-run test",
  },
  "betterScripts": {
    "test": {
      "command": "jest --coverage",
      "env": {
        "LOG_LEVEL": "silent",
        "NODE_ENV": "test"
      }
    }
  },
  "jest" : { ... }
  ...

With majestic, I cannot set these in the UI since there is no such option and majestic seems to be not using the npm scripts.

[Raathigesh]

This is addressed with the rewrite. https://github.com/Raathigesh/majestic#optional-configuration

[mrchief]

You could but then I see 2 issues with that:

• possible duplication of props: you have to declare and maintain same set of vars in 2 places since most projects will have and continue to keep the option of running via CLI (my betterScripts is one such example)

• takes it further away from being zero-config

Most people have npm test or yarn test configured to run in a certain way. By hooking into that (assuming you have a way of doing that), majestic, “instantly” becomes compatible with virtually every react project in the world. Zero config is the biggest selling point here - I’d suggest to keep it that way .

Eventually, I do see the need of your own separate section but for this specific request, I wouldn’t go that way.