Repository navigation
Support test automation exclusions in Karate - #12945
calvinbayer wants to merge 2 commits into
Conversation
202e7f7 to
68b3c9f
Compare
68b3c9f to
9fda4c1
Compare
CI Visibility Test Environment - sbt-scalatestJob Status: 🟢 success
Baseline: median of Tests run to verify that CI Visibility behavior has not regressed in the current PR. |
CI Visibility Test Environment - nebula-release-pluginJob Status: 🟢 success
Baseline: median of Tests run to verify that CI Visibility behavior has not regressed in the current PR. |
CI Visibility Test Environment - heliboardJob Status: 🟢 success
Baseline: median of Tests run to verify that CI Visibility behavior has not regressed in the current PR. |
CI Visibility Test Environment - netflix-zuulJob Status: 🟢 success
Baseline: median of Tests run to verify that CI Visibility behavior has not regressed in the current PR. |
CI Visibility Test Environment - pass4sJob Status: 🟢 success
Baseline: median of Tests run to verify that CI Visibility behavior has not regressed in the current PR. |
CI Visibility Test Environment - reactive-streams-jvmJob Status: 🟢 success
Baseline: median of Tests run to verify that CI Visibility behavior has not regressed in the current PR. |
CI Visibility Test Environment - sonar-kotlinJob Status: 🟢 success
Baseline: median of Tests run to verify that CI Visibility behavior has not regressed in the current PR. |
CI Visibility Test Environment - jolokiaJob Status: 🟢 success
Baseline: median of Tests run to verify that CI Visibility behavior has not regressed in the current PR. |
CI Visibility Test Environment - okhttpJob Status: 🟢 success
Baseline: median of Tests run to verify that CI Visibility behavior has not regressed in the current PR. |
CI Visibility Test Environment - spring_bootJob Status: 🟢 success
Baseline: median of Tests run to verify that CI Visibility behavior has not regressed in the current PR. |
🟢 Java Benchmark SLOs — All performance SLOs passed
PR vs. master results
Commit: Load and DaCapo benchmarks can be triggered manually in the GitLab pipeline. Results will appear in the Benchmarking Platform UI after completion. |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
CI Visibility Test Environment - sonar-javaJob Status: 🟢 success
Baseline: median of Tests run to verify that CI Visibility behavior has not regressed in the current PR. |
There was a problem hiding this comment.
More details
Both Karate adapters now pass scenario tags into exclusion-aware skip decisions, consistent with existing retry policy selection and reporting. The completed static review identified no actionable regressions.
🤖 Bits Code Review · Commit 9fda4c1
9fda4c1 to
1b32475
Compare
|
@autotest Review |
There was a problem hiding this comment.
More details
Scenario exclusion tags reach skip-policy selection in both Karate versions, consistent with the existing execution-policy and reporting paths.
🤖 Bits Code Review · Commit 5186251
5186251 to
17a769a
Compare
|
@autotest Review |
There was a problem hiding this comment.
More details
Both Karate integrations now pass effective scenario tags into skip-policy selection, consistent with the existing retry and reporting paths.
🤖 Bits Code Review · Commit 17a769a
17a769a to
072b0d2
Compare
|
@autotest Review |
There was a problem hiding this comment.
More details
Both Karate integrations supply skip selection with the same effective scenario tags already used by execution policy and reporting, preserving exclusion handling and assigned Test Management properties. The completed static review identified no actionable regression.
🤖 Bits Code Review · Commit 072b0d2
072b0d2 to
21b929b
Compare
|
@autotest Review |
There was a problem hiding this comment.
More details
Both Karate integrations now pass scenario tags into exclusion-aware skip selection, consistent with their retry and reporting policies. The completed static review identified no reportable defects.
🤖 Bits Code Review · Commit 21b929b
21b929b to
f79b33e
Compare
|
@autotest Review |
There was a problem hiding this comment.
More details
Both Karate adapters consistently pass scenario tags into the existing exclusion-aware skip policy. Static review found no actionable defect in that wiring or the added exclusion regressions.
🤖 Bits Code Review · Commit f79b33e
Shepherd verification — Karate exclusions and packaged-agent smokeTested by: Shepherd Agent (autonomous QA for Datadog Test Optimization)
Native tasks were forced to execute on JDK 21, with fresh XML results. An initial host-default JDK 25 run skipped the unsupported Karate 1.x containers; those skips were not counted as verification and the supported-JDK matrix was rerun. The native exclusion cases verify protected scenario execution/failure, exclusion tags and retained Test Management assignment tags. The packaged smoke used the normal Shepherd Crook workflow with Scope: Native Karate instrumentation tests exercise the Karate behavior. Jolokia is a cross-framework Java/TestNG packaged-agent smoke; it is not a Karate workload. Data was verified through local Mockdog assertions, not the production backend or Datadog UI. No backend API request/response/parsing changes were found in this PR's eight-file diff. Issues found: No additional Karate behavior bug was found. Dani's substantive shared/API recommendations are already inherited, and scenario categories are already reused. The remaining double blank lines in the two native test files are cosmetic and were left unchanged. CI note: GitHub's pending Normal Crook cleanup removed the injected agent and stopped its owned Mockdog process. Port 5259 was verified free, playground state (including the pre-existing |
f79b33e to
a8e03cf
Compare
e9b225d to
0d3ce18
Compare
0d3ce18 to
004ac89
Compare
What Does This Do
Support test automation exclusions in Karate. Wire test declaration metadata into Datadog policy selection and reporting, preserving assigned Test Management properties.
Motivation
Allow individual tests to prevent Datadog quarantine/disabling and exclude Datadog ATR, EFD and Attempt to Fix. Developer selection and framework retries retain their existing semantics.
Additional Notes
Stacked on
codex/cucumber-automation-exclusions; review this PR against its base for the framework-specific change. Shared public API and policy are introduced by the first JUnit4 PR.Validation: Both Karate1 and Karate2 module spotlessApply and instrumented exclusion regressions passed on installed JDK21. Each protected scenario executes once with blocking failure, annotation tags and preserved assignment tags.
Snapshot dependency for inherited physical source paths: DataDog/test-environment#604.
test-environment-branch: codex/java-inherited-test-source-snapshots