-
Notifications
You must be signed in to change notification settings - Fork 154
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
Improve the integration tests framework documentation #5461
Conversation
Pinging @elastic/elastic-agent (Team:Elastic-Agent) |
This pull request does not have a backport label. Could you fix it @belimawr? 🙏
NOTE: |
This pull request is now in conflicts. Could you fix it? 🙏
|
a4a2f16
to
0dbc325
Compare
|
Pinging @elastic/elastic-agent-control-plane (Team:Elastic-Agent-Control-Plane) |
|
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.
Looks good as far as I can tell, but I'd prefer someone more familiar with the framework to review too.
It seems this PR is waiting on SonarQube even though it only changes documentation. 🤔 I enabled auto-merge and I'll look more into it tomorrow. |
No need for SonarQube check on this docs-only PR. Force merging... |
* Improve the integration tests framework documentation * Fix typo (cherry picked from commit d99b09b)
What does this PR do?
It improves the integration tests framework documentation on how to debug test from the remove VMs.
Why is it important?
It improves the integration tests framework documentation on how to debug test from the remove VMs.
Checklist
[ ] My code follows the style guidelines of this project[ ] I have commented my code, particularly in hard-to-understand areas[ ] I have made corresponding change to the default configuration files[ ] I have added tests that prove my fix is effective or that my feature works[ ] I have added an entry in./changelog/fragments
using the changelog tool[ ] I have added an integration test or an E2E test## Disruptive User Impact## How to test this PR locally## Related issuesQuestions to ask yourself