-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Added server api tests for event log service #63540
Added server api tests for event log service #63540
Conversation
Pinging @elastic/kibana-alerting-services (Team:Alerting Services) |
…functional-tests # Please enter a commit message to explain why this merge is necessary, # especially if it merges an updated upstream into a topic branch. # # Lines starting with '#' will be ignored, and an empty message aborts # the commit.
…functional-tests # Please enter a commit message to explain why this merge is necessary, # especially if it merges an updated upstream into a topic branch. # # Lines starting with '#' will be ignored, and an empty message aborts # the commit.
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.
Changes LGTM, I have a few notes to avoid flakiness. I'd like @pmuellr to also review this PR to make sure it tests what he hoped for in the issue.
x-pack/test/plugin_api_integration/test_suites/event_log/service_api_integration.ts
Outdated
Show resolved
Hide resolved
x-pack/test/plugin_api_integration/test_suites/event_log/service_api_integration.ts
Outdated
Show resolved
Hide resolved
x-pack/test/plugin_api_integration/test_suites/event_log/service_api_integration.ts
Outdated
Show resolved
Hide resolved
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.
This is looking pretty good! I made a note about not needing the start/stop timing - I think - but doing a test of those slightly differently. There are a number of logger.info()
's which I assume will get cleaned up before merge.
I'm a little worried about flakiness, given the async nature of the logger, suggest we run this through the flaky test runner. In the future, when we buffer events instead of just writing them individually in async fashion, things will get even flakier - but we'll worry about that when we get there.
x-pack/test/plugin_api_integration/plugins/event_log/server/init_routes.ts
Show resolved
Hide resolved
x-pack/test/plugin_api_integration/plugins/event_log/server/init_routes.ts
Outdated
Show resolved
Hide resolved
💚 Build SucceededHistory
To update your PR or re-run it, just comment with: |
* Added server api tests for event log service * fixed tests * fixed type check issue * Fixed failing tests * fixed jest tests * Fixed due to comments * Removed flackiness tests * fixed type check error * Fixed func test
* Added server api tests for event log service * fixed tests * fixed type check issue * Fixed failing tests * fixed jest tests * Fixed due to comments * Removed flackiness tests * fixed type check error * Fixed func test
* Added server api tests for event log service (#63540) * Added server api tests for event log service * fixed tests * fixed type check issue * Fixed failing tests * fixed jest tests * Fixed due to comments * Removed flackiness tests * fixed type check error * Fixed func test * fixed compatibility issues * fixed type check
Resolve #55642