Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Add support for multiple jest runners in one project

See original GitHub issue

Suppose having different jest configs for unit and e2e tests. Whenever running tests in majestic GUI majestic config in package.json has to be changed. How about switching from:

"majestic": {
    "jestScriptPath": "./node_modules/jest/bin/jest.js",
    "args": ["--config=./config/jest/e2e.json"]
}

to something like this:

"majestic": {
    "jestScriptPath": "./node_modules/jest/bin/jest.js",
    "runners": {
        "unit": ["--config=./config/jest/unit.json"],
        "e2e": ["--config=./config/jest/e2e.json"]
    }
}

Issue Analytics

State:
Created 4 years ago
Comments:5 (5 by maintainers)

Top GitHub Comments

1reaction

MacZelcommented, Apr 7, 2019

That’s exactly what I meant

1reaction

Raathigeshcommented, Apr 7, 2019

How about having named configs like below

"majestic": {
    "jestScriptPath": "./node_modules/jest/bin/jest.js",
    "configs": {
         "unit": {
             "args": [],
              "env": {}
          },
        "e2e": {
             "args": [],
              "env": {}
          }
     }
}

and then when starting Majestic you could pass a flag like --config=unit?