-
Notifications
You must be signed in to change notification settings - Fork 403
[Test Case] - Verify logs of observability components #9634
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
Comments
This issue has been automatically marked as stale due to the lack of recent activity. It will soon be closed if no further activity occurs. Thank you for your contributions. |
This issue has been automatically marked as stale due to the lack of recent activity. It will soon be closed if no further activity occurs. Thank you for your contributions. |
This issue has been automatically marked as stale due to the lack of recent activity. It will soon be closed if no further activity occurs. Thank you for your contributions. |
This issue has been automatically marked as stale due to the lack of recent activity. It will soon be closed if no further activity occurs. Thank you for your contributions. |
This issue has been automatically closed due to the lack of recent activity. |
This issue has been automatically marked as stale due to the lack of recent activity. It will soon be closed if no further activity occurs. Thank you for your contributions. |
With the removal of the monitoring component, this test case is obsolete |
Summary
The purpose of the test is to assure that there are no unexpected error logs in our components indicating potentially real issues
Automation Steps
Have a new test case that verifies all logs of our components and asserts on new error messages. There must be a way to whitelist errors.
The test case should be integrated into all typical test suites without having the assertion activated (only printing the results). At a later stage, we will activate the assertion.
There should be a new pre-submit job that is triggered only for our components which will assert
Manual Test Cases
The text was updated successfully, but these errors were encountered: