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
Remove spam from test-backend output #15769
Conversation
8bbdbd3
to
0789a93
Compare
0789a93
to
ffa5d45
Compare
ffa5d45
to
c146507
Compare
c79850a
to
e1e7e0e
Compare
292edaa
to
7b4326d
Compare
@timabbott Please give an initial review on this much work. |
e089825
to
587f093
Compare
This commit tests logging of warning log using assertLogs instead of printing it in test output hence avoiding spam in test output.
This commit tests logging of warning log using assertLogs instead of printing it in test output hence avoiding spam in test output.
This commit tests logging of warning and debug logs in code related to social auth with ldap using assertLogs. So it does not get printed in the test output hence avoiding spam in the test output.
This commit tests logging of info log using assertLogs instead of printing it in test output hence avoiding spam in test output.
This commit tests logging of warning log using assertLogs instead of printing it in test output hence avoiding spam in test output.
This commit tests logging of warning log using assertLogs instead of printing it in test output hence avoiding spam in test output.
This commit tests logging of debug log using assertLogs instead of printing it in test output hence avoiding spam in test output.
…ectly. This commit tests logging of info log using assertLogs instead of printing it in test output hence avoiding spam in test output.
This commit tests logging of warning log using assertLogs instead of printing it in test output hence avoiding spam in test output.
This commit tests logging of warning log while updating ldap user's custom profile field with invalid data using assertLogs instead of printing it in test output hence avoiding spam in test output.
This commit tests logging of warning log while updating user's custom profile field not present in ldap using assertLogs instead of printing it test output hence avoiding spam in test output.
This commit tests logging of warning log while updating ldap user's non existing custom profile field using assertLogs instead of printing it in test output hence avoiding spam in test output.
This commit tests logging of debug logs while LDAP login failure due to domain mismatch using assertLogs instead of printing it in test output hence avoiding spam in test output.
This commit verify error logs printed during testing of log_and report function using assertLogs without printing it in test output and hence avoiding spam.
This commit verify warning logs while testing validate_api_key and profile is incoming webhook but is_webhook is not set to True. Verification is done using assertLogs so that logs does not cause spam by printing in the test output.
This commit tests if error logs are logged when an error occurs during testing of check_send_webhook_fixture_message using assertlogs. Using assertlogs ensure logs are not printed as spam in test output.
This commit verify that error logging while testing data export in test_notify_realm_export_on_failure using assertLogs so that the logs do not spam test output.
This commits verify error logs while simulate_error simulates an error using assertLogs so that the logs do not spam the test ouptut.
This commit tests if info logs are logging using assertLogs so that the log do not spam the test output.
ERROR_BOT setting is not None during testing, so running test_report_error without making errors stream was causing exception. This commit make a stream name errors thus removes exception and error log spam caused by it in ./tools/test-backend output.
This commit verifies info logging in test_fix_unreads using assertLogs so that the logging do not spam ./tools/test-backend output.
This commit verify error logging using assertLogs so logs do not spam ./tools/test-backend output.
587f093
to
9861937
Compare
@thedeveloperr you can potentially go back to this PR now that we've merged most of the prep commits. |
Heads up @thedeveloperr, we just merged some commits that conflict with the changes your made in this pull request! You can review this repository's recent commits to see where the conflicts occur. Please rebase your feature branch against the |
Most of commits from this PR have been merged. Rest are in different PRs so closing this. |
#1587
Testing Plan:
GIFs or Screenshots: