Skip to content
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

Update how-to-write-tests-for-plugins.md #299

Merged
merged 1 commit into from
Jan 21, 2025
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/how-to-write-tests-for-plugins.md
Original file line number Diff line number Diff line change
Expand Up @@ -157,9 +157,9 @@ classes that need to do the muzzle check.
Instrumentation tests are generally run against the lowest version of a library that we support to ensure a baseline
against users with old dependency versions. Due to the nature of the agent and locations where we instrument private
APIs, the agent may fail on a newly released version of the library. We run instrumentation tests additionally against
the latest version of the library, as fetched from Maven, as part of a nightly build. If a new version of a library will
the latest version of the library, as fetched from remote, as part of a nightly build. If a new version of a library will
not work with the agent, we find out through this build and can address it by the next release of the agent.

Users can add a muzzle check case by calling `NewLatestDepthTestCase`, the arguments taken by `NewLatestDepthTestCase`
are almost the same as `NewGeneralTestCase`. You need to additionally specify the dependency name of the plugin and the list of
classes that need to do the latest-depth check.
classes that need to do the latest-depth check.
Loading