-
Notifications
You must be signed in to change notification settings - Fork 524
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
Migrate more system tests to Go #4469
Conversation
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
Steps errorsExpand to view the steps failures
|
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.
Removing the extra tests for apm-server.instrumentation
is fine.
Just a nit - please remove the libbeat_instrumentation_enabled
parts from the tests/system/config/apm-server.yml.j2
Codecov Report
@@ Coverage Diff @@
## master #4469 +/- ##
==========================================
+ Coverage 75.95% 75.97% +0.02%
==========================================
Files 161 161
Lines 9787 9787
==========================================
+ Hits 7434 7436 +2
+ Misses 2353 2351 -2
|
Done, thanks for the nudge |
* systemtest: migrate profiling tests to Go * systemtest: migrate remaining instrumentation * systemtest: migrate another sampling-related test * systemtest: migrate some API Key command tests * tests/system/config: drop instrumentation bits
* systemtest: migrate profiling tests to Go * systemtest: migrate remaining instrumentation * systemtest: migrate another sampling-related test * systemtest: migrate some API Key command tests * tests/system/config: drop instrumentation bits Co-authored-by: Andrew Wilkins <[email protected]>
Motivation/summary
Migrate more system tests to Go. With the instrumentation tests, I deleted the tests for deprecated instrumentation config, and only test the new libbeat instrumentation config.
Checklist
- [ ] I have updated CHANGELOG.asciidocI have considered changes for:
- [ ] documentation- [ ] logging (add log lines, choose appropriate log selector, etc.)- [ ] metrics and monitoring (create issue for Kibana team to add metrics to visualizations, e.g. Kibana#44001)- [ ] telemetry- [ ] Elasticsearch Service (https://cloud.elastic.co)- [ ] Elastic Cloud Enterprise (https://www.elastic.co/products/ece)- [ ] Elastic Cloud on Kubernetes (https://www.elastic.co/elastic-cloud-kubernetes)How to test these changes
cd systemtest && go test -v
Related issues
None.