chore: convenient script to filter tests #6787
Conversation
| /* eslint-disable @typescript-eslint/restrict-template-expressions */ | ||
|
|
There was a problem hiding this comment.
I don't remember making this change.
|
Could you describe in |
pkg-manager/core/package.json
Outdated
| @@ -144,9 +144,11 @@ | |||
| "registry-mock": "registry-mock", | |||
| "test:jest": "jest", | |||
| "test:e2e": "registry-mock prepare && run-p -r registry-mock test:jest", | |||
| "filtered-test:jest": "sh -o nounset -c 'jest --verbose --testPathPattern \"$TEST_PATH_PATTERN\" --testNamePattern \"$TEST_NAME_PATTERN\"'", | |||
There was a problem hiding this comment.
How would this work? The registry-mock is not started.
There was a problem hiding this comment.
So that why successful offline installation test didn't finish!
Anyway, with the latest commits, I have merged filtered-test into test. The environment variables have been made optional.
There was a problem hiding this comment.
Also, since I merge filterered-test into test, test now requires sh even on Windows. Do you prefer creating a JavaScript file to spawn the test cross-platform?
|
I have found the right way to do this, using jest's setup and teardown scripts: #6813 |
so that we don't need to edit the source code (adding
.onlyto the test file and file path to the script) and the undo it over and over again.