-
Notifications
You must be signed in to change notification settings - Fork 17
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
Understand why it takes so long to pass the tests #690
Labels
code health
Improve code readability, simplify maintenance and so on
Comments
LeonidVas
added
the
code health
Improve code readability, simplify maintenance and so on
label
Jun 7, 2022
Some thoughts about possible fixes (to make the situation with tests more acceptable):
|
Made a table with information about testing times, suggestions and flaky tests. Preview with longest tests:
|
better0fdead
added a commit
that referenced
this issue
Jul 4, 2022
Separated integration tests from linter, unit, e2e and examples checks. Part of #690
better0fdead
added a commit
that referenced
this issue
Jul 4, 2022
Separated integration tests from linter, unit, e2e and examples checks. Part of #690
better0fdead
added a commit
that referenced
this issue
Jul 14, 2022
Separated integration tests from linter, unit, e2e and examples checks, because integration tests run longer then all other. Result: 15% faster testing. Part of #690
LeonidVas
pushed a commit
that referenced
this issue
Jul 15, 2022
Separated integration tests from linter, unit, e2e and examples checks, because integration tests run longer then all other. Result: 15% faster testing. Part of #690
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Now it takes a very long time to pass the tests (> 1 hour).
What's needed:
The text was updated successfully, but these errors were encountered: