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

E2E Tests improvments #245

Open
MalloZup opened this issue Mar 3, 2021 · 0 comments
Open

E2E Tests improvments #245

MalloZup opened this issue Mar 3, 2021 · 0 comments
Labels

Comments

@MalloZup
Copy link
Contributor

MalloZup commented Mar 3, 2021

This epic wants to track from highlevel pov what we might tackle as steps to improve E2E test experience.

Feel free to extend this epic

Coverage:

Goal of this is to improve the testing coverage of hawk. Normally it has more priority over improvements of the testing framework/refactorings etc.

    1. check if hawk is consuming more then 90%cpu during the testsuite ( this was a bug in the past)

Testing framework/Tests

  1. Have a summary minimalistic, colored output on terminal. (investigate the adoption of pylint)
@MalloZup MalloZup added the epic label Mar 3, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant