Fixing the JEST config for IDEs
What does this MR do?
NEW:
The environment flag won't work (see comments)
So to keep preexisting references from breaking, we simply rename jest.config.unit.js
to jest.config.js
.
ORIGINAL:
Updates the Jest configuration so that instead of two different configs (introduced in !31984 (merged)) we would get the default jest.config.js
back for the IDEs to work out of the box. However, we expect an eventual INTEGRATION
environment flag to run integration tests whenever we need that.
Screenshots
Does this MR meet the acceptance criteria?
Conformity
-
Changelog entry -
Documentation (if required) -
Code review guidelines -
Merge request performance guidelines -
Style guides -
Database guides -
Separation of EE specific content
Availability and Testing
-
Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process. -
Tested in all supported browsers -
Informed Infrastructure department of a default or new setting change, if applicable per definition of done
Security
If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:
-
Label as security and @ mention @gitlab-com/gl-security/appsec
-
The MR includes necessary changes to maintain consistency between UI, API, email, or other methods -
Security reports checked/validated by a reviewer from the AppSec team
Edited by Paul Slaughter