Skip to content
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

Local testing experience #39085

Closed
9 of 10 tasks
jbudz opened this issue Jun 17, 2019 · 2 comments
Closed
9 of 10 tasks

Local testing experience #39085

jbudz opened this issue Jun 17, 2019 · 2 comments
Assignees
Labels
Team:Operations Team label for Operations Team

Comments

@jbudz
Copy link
Member

jbudz commented Jun 17, 2019

Issues

Exploration

  • Speed
    • Can functional tests be rewritten to minimize timeouts?
    • Can we improve startup time? (iffy - this is probably babel/register related)
    • Find and replace unit tests not using mock http and fs calls
  • Organization
    • Can we make the configuration inheritance easier to trace?

Part of the development experience issue tracked at #34557

@jbudz jbudz added the Team:Operations Team label for Operations Team label Jun 17, 2019
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-operations

@joshdover
Copy link
Contributor

Regarding speed, I wonder if we should ratchet down the default jest test timeout and/or introduce a "slow test warning" in order to keep our main unit test suite fast. Tests that show up in this list should either be refactored to use mocks (as suggested above) or moved into the jest integration suite if they truly need to exercise slower code paths.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Team:Operations Team label for Operations Team
Projects
None yet
Development

No branches or pull requests

4 participants