Exposes globalConfig to custom test sequencers #14535
Conversation
✅ Deploy Preview for jestjs ready!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site configuration. |
| sequencer = new TestSequencer({ | ||
| contexts: [], | ||
| globalConfig: {} as Config.GlobalConfig, | ||
| }); |
There was a problem hiding this comment.
Not sure if this is ideal, but since the Jest TestSequencer doesn't use either contexts, or globalConfig, it should be fine to have stand ins here, for now.
Alternatively we could make TestSequencerOptions optional, or even properly create contexts and globalConfig in the beforeEach.
lmk what you think.
There was a problem hiding this comment.
in this test you can use
jest/packages/test-utils/src/config.ts
Line 131 in 0afd8f1
But it might need to be optional so it's not a breaking change (i.e. a newer version of @jest/test-scheduler than the version of @jest/core). However, I think the next release of Jest will be a major, in which case we don't need it to be optional.
|
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Summary
Adds a way for custom test sequencers to access the global config. This will allow ordering test suites by using the seed which I don't see an easy way to do currently.
Test plan
Added unit tests to check that we can use globalConfig values, namely
seed, in a customTestSequencer.yarn jest e2e/__tests__/customTestSequencers.test.ts