Skip to content

Migrate feature-flagging groovy tests to java#11716

Merged
gh-worker-dd-mergequeue-cf854d[bot] merged 14 commits into
masterfrom
sarahchen6/migrate-feature-flagging-tests-to-java
Jun 26, 2026
Merged

Migrate feature-flagging groovy tests to java#11716
gh-worker-dd-mergequeue-cf854d[bot] merged 14 commits into
masterfrom
sarahchen6/migrate-feature-flagging-tests-to-java

Conversation

@sarahchen6

@sarahchen6 sarahchen6 commented Jun 23, 2026

Copy link
Copy Markdown
Contributor

What Does This Do

Migrate Groovy tests in the products module to Java without changing any functionality

Motivation

This is part of a broader initiative to migrate all testing in this repo to JUnit

Additional Notes

Confirmation that we did not lose tests (note that a few tests were combined in this PR):

Contributor Checklist

  • Format the title according to the contribution guidelines
  • Assign the type: and (comp: or inst:) labels in addition to any other useful labels
  • Avoid using close, fix, or any linking keywords when referencing an issue
    Use solves instead, and assign the PR milestone to the issue
  • Update the CODEOWNERS file on source file addition, migration, or deletion
  • Update public documentation with any new configuration flags or behaviors
  • Add your completed PR to the merge queue by commenting /merge. You can also:
    • Customize the commit message associated with the merge with /merge --commit-message "..."
    • Remove your PR from the merge queue with /merge -c
    • Skip all merge queue checks with /merge -f --reason "reason"; please use this judiciously, as some checks do not run at the PR-level (note: the PR still needs to be mergeable, this will only skip the pre-merge build)
    • Get more information in this doc

Jira ticket: [PROJ-IDENT]

@sarahchen6 sarahchen6 added comp: testing Testing tag: no release notes Changes to exclude from release notes tag: ai generated Largely based on code generated by an AI or LLM labels Jun 23, 2026
@dd-octo-sts

dd-octo-sts Bot commented Jun 23, 2026

Copy link
Copy Markdown
Contributor

🟢 Java Benchmark SLOs — All performance SLOs passed

Suite Status
Startup 🟢 pass

SLO thresholds are defined here based on automatically generated metrics. A warning is raised when results are within 5% of the threshold.

PR vs. master results
Scenario Candidate master Δ (95% CI of mean)
startup:insecure-bank:iast:Agent 13.98 s 13.97 s [-0.7%; +0.8%] (no difference)
startup:insecure-bank:tracing:Agent 12.83 s 12.97 s [-1.7%; -0.4%] (maybe better)
startup:petclinic:appsec:Agent 17.39 s 17.19 s [+0.3%; +2.0%] (maybe worse)
startup:petclinic:iast:Agent 16.83 s 17.47 s [-7.8%; +0.5%] (no difference)
startup:petclinic:profiling:Agent 17.34 s 17.27 s [-0.5%; +1.4%] (no difference)
startup:petclinic:sca:Agent 17.48 s 16.59 s [+1.2%; +9.5%] (significantly worse)
startup:petclinic:tracing:Agent 16.53 s 16.59 s [-1.3%; +0.5%] (no difference)

Commit: c06b654a · CI Pipeline · Benchmarking Platform UI


Load and DaCapo benchmarks can be triggered manually in the GitLab pipeline. Results will appear in the Benchmarking Platform UI after completion.

@sarahchen6 sarahchen6 marked this pull request as ready for review June 23, 2026 21:11
@sarahchen6 sarahchen6 requested a review from a team as a code owner June 23, 2026 21:11
@sarahchen6 sarahchen6 requested review from sameerank and typotter and removed request for a team June 23, 2026 21:11
return fieldType.cast(field.get(target));
}

private static void eventually(ThrowingRunnable assertion, long timeoutMillis) throws Exception {

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💭 thought: ‏That might be the kind of utility methods that should go in test-utils modules. WDYT?

@sarahchen6 sarahchen6 Jun 24, 2026

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It looks like this file is the only use case for eventually, so may not be worth adding to a shared space 🤔

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's keep it that way, I will start a discussion on the Slack channel because I think I found similar usage in the code base already. Don't sweat too much about it for this PR (out of scope).

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I added the capability here and added you as reviewer: #11739
You can wait for it to be merged or I will follow up with another PR to use it in this test suite.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sounds good, thanks! I can wait for it to be merged and update this PR directly then

@sarahchen6 sarahchen6 requested a review from PerfectSlayer June 24, 2026 20:41

@PerfectSlayer PerfectSlayer left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the migration and follow up changes!

I added two minor comments about the newly opened API.

@sarahchen6

Copy link
Copy Markdown
Contributor Author

/merge

@gh-worker-devflow-routing-ef8351

gh-worker-devflow-routing-ef8351 Bot commented Jun 26, 2026

Copy link
Copy Markdown

View all feedbacks in Devflow UI.

2026-06-26 17:57:52 UTC ℹ️ Start processing command /merge


2026-06-26 17:57:56 UTC ℹ️ MergeQueue: pull request added to the queue

The expected merge time in master is approximately 1h (p90).


2026-06-26 19:01:48 UTC ℹ️ MergeQueue: This merge request was merged

@gh-worker-dd-mergequeue-cf854d gh-worker-dd-mergequeue-cf854d Bot merged commit a1a064b into master Jun 26, 2026
582 checks passed
@gh-worker-dd-mergequeue-cf854d gh-worker-dd-mergequeue-cf854d Bot deleted the sarahchen6/migrate-feature-flagging-tests-to-java branch June 26, 2026 19:01
@github-actions github-actions Bot added this to the 1.64.0 milestone Jun 26, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

comp: testing Testing tag: ai generated Largely based on code generated by an AI or LLM tag: no release notes Changes to exclude from release notes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants