-
Notifications
You must be signed in to change notification settings - Fork 8.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[test] consolidate top level npm scripts #41133
Labels
chore
enhancement
New value added to drive a business result
Team:Operations
Team label for Operations Team
Comments
mistic
added
enhancement
New value added to drive a business result
Team:Operations
Team label for Operations Team
labels
Jul 15, 2019
Pinging @elastic/kibana-operations |
jbudz
added a commit
to jbudz/kibana
that referenced
this issue
Jan 27, 2020
Over the last few years we've increased the number of test runners. Entry points by test type have become too lage of a category for unique names, so this moves top level test scripts under yarn and replaces test types with the runner name. e.g. `yarn test:browser` -> `yarn test:karma` Closes elastic#41133
jbudz
added a commit
to jbudz/kibana
that referenced
this issue
Jan 27, 2020
Over the last few years we've increased the number of test runners. Entry points by test type have become too lage of a category for unique names, so this moves top level test scripts under yarn and replaces test types with the runner name. e.g. `yarn test:browser` -> `yarn test:karma` Closes elastic#41133
jbudz
added a commit
that referenced
this issue
Feb 18, 2020
Over the last few years we've increased the number of test runners. Entry points by test type have become too lage of a category for unique names, so this moves top level test scripts under yarn and replaces test types with the runner name. e.g. `yarn test:browser` -> `yarn test:karma` Closes #41133 Co-authored-by: Elastic Machine <[email protected]>
7 tasks
jbudz
added a commit
that referenced
this issue
Feb 21, 2020
* Refactor test entry by runner (#44679) Over the last few years we've increased the number of test runners. Entry points by test type have become too lage of a category for unique names, so this moves top level test scripts under yarn and replaces test types with the runner name. e.g. `yarn test:browser` -> `yarn test:karma` Closes #41133 Co-authored-by: Elastic Machine <[email protected]> * fix merge Co-authored-by: Elastic Machine <[email protected]>
spalger
pushed a commit
to spalger/kibana
that referenced
this issue
May 15, 2020
Over the last few years we've increased the number of test runners. Entry points by test type have become too lage of a category for unique names, so this moves top level test scripts under yarn and replaces test types with the runner name. e.g. `yarn test:browser` -> `yarn test:karma` Closes elastic#41133 Co-authored-by: Elastic Machine <[email protected]> # Conflicts: # packages/kbn-plugin-generator/sao_template/template/README.md # packages/kbn-plugin-helpers/lib/tasks.js # test/scripts/jenkins_xpack.sh
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
chore
enhancement
New value added to drive a business result
Team:Operations
Team label for Operations Team
Currently npm scripts are a mixed combination of either the test type or the test framework. Lets package all of the under the test framework.
The text was updated successfully, but these errors were encountered: