appsec: add smoke tests for apm standalone#6181
Conversation
|
|
8b69cf1 to
e67144b
Compare
|
✨ Fix all issues with BitsAI or with Cursor
|
20a2e93 to
8a60060
Compare
fd4926c to
8679f7a
Compare
e58bf30 to
834583e
Compare
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 834583e22b
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: aba9c84c94
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
cbeauchesne
left a comment
There was a problem hiding this comment.
Just a small naming request, then all good.
aba9c84 to
0326ddd
Compare
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 0326ddddad
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
0326ddd to
09567d7
Compare
09567d7 to
6888a95
Compare
…s flaky Separate test classes for each scenario so they can have independent manifest declarations: - Test_AppSecAPMStandalone_*: APPSEC_APM_STANDALONE (tracing enabled) - Test_AppSecStandaloneAPMStandalone_*: APPSEC_STANDALONE_APM_STANDALONE (tracing disabled — traces without appsec data silently dropped) Both sets use identical clean base classes with no workarounds. The Java standalone variants for Threats, Rasp, ApiSecurity, and UserEvents are marked flaky (APPSEC-60872): the Java tracer drops traces from the first request to each code path when DD_APM_TRACING_ENABLED=false. Updated manifests: java, golang, nodejs, php, ruby, cpp_nginx. File-level entries (dotnet, python, agent) already cover both class sets. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
6888a95 to
2a6383a
Compare
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 2a6383aa34
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
|
||
| """AppSec smoke tests for the appsec_apm_standalone scenario.""" | ||
|
|
||
| from utils import interfaces, remote_config as rc, weblog |
There was a problem hiding this comment.
Just to understand, why do you need base classes here?
There was a problem hiding this comment.
So the comment should be removed, thanks for spotting it. Base classes are more generic than just apm standalone.
The idea is to have base classes for generic smoke tests and instantiate them for each configuration we want to test (the first two being "apm standalone" and "apm standalone + appsec standalone" in this PR).
My point is to be able to instantiate the same test in different scenarios and be able to have different manifest entries for each test in each scenario. To allow passing the same test with a configuration but not necessarily with another.
Is there a more idiomatic way to handle this ?
Motivation
Test that AppSec is correctly enabled and functional in APM Standalone mode (with infra disabled at the agent level).
To do so, I setup a testing class that performs AAP smoke tests using only data intercepted at the agent level. This testing class can then be used through inheritance to create different test suites linked to different features and manifest entries.
Changes
interfaces.agentto perform assertions on traces intercepted after the agent=> This ensures that all communication protocols used by AAP (traces, trace stats, telemetry and RC) keep getting proxied by the agent.
Workflow
🚀 Once your PR is reviewed and the CI green, you can merge it!
🛟 #apm-shared-testing 🛟
Reviewer checklist
tests/ormanifests/is modified ? I have the approval from R&P teambuild-XXX-imagelabel is present