feat(tests): splitting integration tests #503
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
geekbrother
changed the title
geekbrother
force-pushed
the
feat/split_integration_tests
branch
from
b718977 to
ae27807
Compare
geekbrother
commented
Feb 6, 2024
| @@ -0,0 +1,5 @@ | |||
| { | |||
| "compilerOptions": { | |||
| "esModuleInterop": true | |||
There was a problem hiding this comment.
This is a fix for the following warning:
ts-jest[config] (WARN) message TS151001: If you have issues related to imports, you should consider setting `esModuleInterop` to `true` in your TypeScript configuration file (usually `tsconfig.json`). See https://blogs.msdn.microsoft.com/typescript/2018/01/31/announcing-typescript-2-7/#easier-ecmascript-module-interoperability for more information.
arein
approved these changes
Feb 6, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR splits Jest integration tests from one huge file into
endpoint per fileapproach.As the integration tests are growing and a large amount of lines for tests (especially for the new ENS endpoints) are added, the single integration test file becomes unmaintainable. It's better to split it.
The following changes are made:
integration.test.tsis removed,init.tsis created for a common test setup,generators.test.ts,health.test.ts,history.test.ts,identity.test.ts,middlewares.test.ts,names.test.ts,portfolio.test.ts,proxy.test.tstest files are created.How Has This Been Tested?
Run these tests for a prod endpoint:
The expected result:
Due Diligence