-
Notifications
You must be signed in to change notification settings - Fork 65
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
[tests] Added for selenium tests for opening visualizers #165 #175
[tests] Added for selenium tests for opening visualizers #165 #175
Conversation
d392938
to
50d9c15
Compare
50d9c15
to
a8f844a
Compare
a8f844a
to
1afbb32
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I stress tested this a bit, added an error on purpose in the JS code for the admin part, and the non-admin test is failing as well because the error log is not getting cleared.
Please stress test your tests to make sure they fail properly.
If we break one view on purpose, only the test for that view should fail.
Then it's the turn of the other view.
Then both.
Remember: break the code on purpose to check your tests catch the failures.
Tests are code too and their effectivness needs to be ensured.
cdb6522
to
26e2b4a
Compare
Added a workaround in the `tearDown` method that clears the web driver console logs after each test. Source: https://stackoverflow.com/questions/44991009/clear-chrome-browser-logs-in-selenium-python
26e2b4a
to
b91afc8
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks 👍
Closes #165