Skip to content

AWS Transform: unit-test generation choice + status-only UT substeps - #2857

Open
Rajanna-Karthik wants to merge 3 commits into
mainfrom
mehishar/feature-d-isstatusonly
Open

AWS Transform: unit-test generation choice + status-only UT substeps#2857
Rajanna-Karthik wants to merge 3 commits into
mainfrom
mehishar/feature-d-isstatusonly

Conversation

@Rajanna-Karthik

@Rajanna-Karthik Rajanna-Karthik commented Aug 28, 2026

Copy link
Copy Markdown
Contributor

What this adds

The language-server side of the unit-test generation experience for AWS Transform (.NET). It powers the Visual Studio behavior.

Customers choose up front whether unit tests get generated; this passes that choice to the transformation job and tells the IDE which steps to show as plain progress.

Changes (language server)

1. Carry the customer's unit-test choice to the job

  • Passes the up-front "generate unit tests?" selection through to the transformation so it acts on the right decision.
  • An unselected option is treated as a real "no"; a client that does not offer the option simply keeps today's behavior.

2. Mark unit-test steps as status-only

  • Flags unit-test-generation substeps as status-only so the IDE renders them as plain progress (no checkpoint controls or "View Results"), like the other transformation substeps.

Notes

  • Main merged into the branch cleanly (no conflicts).
  • Backend contract is already shipped; CR-300232958 fixes a related backend issue where an up-front "no" could be overridden mid-job.
  • Includes unit tests covering choice-forwarding (all input states) and status-only rendering.

mehishar and others added 3 commits July 29, 2026 00:03
Mark the direct substeps of the "Generate Unit Tests" step (plan / generate /
merge / coverage) as status-only so the IDE renders them as progress-only rows,
without a checkpoint toggle, "View Results" button, or checkpoint checkbox.

The step data returned by the service has no machine-readable step label, so the
flag is assigned structurally during plan-tree assembly based on the parent
step's name rather than a label prefix. The parent step keeps its normal
checkpoint affordance.
Include GenerateUnitTests in the CreateJob objective only when it is a real boolean,

so clients that omit it keep legacy behavior and an explicit false stays a decline.

Matches shipped backend contract CR-298620129. Adds 4 unit tests.
@Rajanna-Karthik
Rajanna-Karthik requested a review from a team as a code owner August 28, 2026 17:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants