Skip to content

eval: migrate azure-cloud-migrate integration tests to vally eval suites - #3005

Merged
JasonYeMSFT (JasonYeMSFT) merged 4 commits into
microsoft:mainfrom
JasonYeMSFT:jasonyemsft-azure-cloud-migrate-vally-eval
Aug 5, 2026
Merged

eval: migrate azure-cloud-migrate integration tests to vally eval suites#3005
JasonYeMSFT (JasonYeMSFT) merged 4 commits into
microsoft:mainfrom
JasonYeMSFT:jasonyemsft-azure-cloud-migrate-vally-eval

Conversation

@JasonYeMSFT

Copy link
Copy Markdown
Member

Description

Migrate azure-cloud-migrate skill's integration tests to use vally eval suites.

Checklist

  • Tests pass locally (cd tests && npm test)
  • Title has one of the prefixes: fix:, feat:, feature:, chore:, misc:, test:, eval:
  • If modifying skill descriptions: verified routing correctness with integration tests (In tests/, npm run test:integration -- <skill> or npm run test:vally -- --skill <skill>)

Related Issues

#2902

Adds evals/azure-skills/azure-cloud-migrate/eval.yaml with 8 stimuli
migrated from tests/azure-cloud-migrate/integration.test.ts:

Brownfield (tier: full, runs: 1):
- Face-blur Lambda migration — clones aws-samples/serverless-face-blur-service,
  runs migration prompt + follow-up, checks skill invocation and output files
  (migration-status.md, migration-assessment-report.md, src/{app,detectFaces,blurFaces}.js)
- Webapp Lambda migration — clones aws-samples/lambda-refarch-webapp, checks
  skill invocation and migration-status.md / migration-assessment-report.md

Routing (tier: smoke/full, runs: 5, earlyTerminate on skill-call):
- Spring Boot to ACA compatibility assessment (smoke)
- Spring Boot JAR containerization to ACA (full)
- AWS Fargate ECS tasks to ACA (smoke)
- ECS Fargate containers to ACA (full)
- GKE Kubernetes workloads to ACA (smoke)
- Kubernetes manifest conversion to ACA config (full)

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
use vally test in CI
@JasonYeMSFT
JasonYeMSFT (JasonYeMSFT) requested a review from a team as a code owner August 3, 2026 23:07
Copilot AI review requested due to automatic review settings August 3, 2026 23:07
@JasonYeMSFT JasonYeMSFT (JasonYeMSFT) changed the title eval: azure cloud migrate vally eval migration eval: migrate azure cloud migrate integration tests to vally eval suites Aug 3, 2026
@JasonYeMSFT JasonYeMSFT (JasonYeMSFT) changed the title eval: migrate azure cloud migrate integration tests to vally eval suites eval: migrate azure-cloud-migrate integration tests to vally eval suites Aug 3, 2026

Copilot AI 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.

Pull request overview

This PR migrates the azure-cloud-migrate skill’s integration validation from Jest-based tests to a Vally eval suite, and updates CI so the skill runs under the Vally integration path instead of the Jest integration path.

Changes:

  • Removed azure-cloud-migrate Jest trigger tests, integration tests, and their snapshot file.
  • Added a new Vally eval suite at evals/azure-skills/azure-cloud-migrate/eval.yaml covering brownfield migration + routing scenarios.
  • Updated the all-integration workflow to route azure-cloud-migrate away from the Jest integration job and into the Vally job.
Show a summary per file
File Description
tests/azure-cloud-migrate/triggers.test.ts Deletes Jest trigger test coverage for the skill.
tests/azure-cloud-migrate/integration.test.ts Deletes Jest integration tests previously used for live-agent validation.
tests/azure-cloud-migrate/snapshots/triggers.test.ts.snap Removes snapshots tied to the deleted trigger tests.
evals/azure-skills/azure-cloud-migrate/eval.yaml Adds the Vally eval suite intended to replace the deleted Jest integration coverage.
.github/workflows/test-all-integration.yml Routes azure-cloud-migrate to run under Vally instead of Jest integration tests in CI.

Review details

Suppressed comments (1)

evals/azure-skills/azure-cloud-migrate/eval.yaml:103

  • The webapp migration stimulus currently checks for migration-status.md / migration-assessment-report.md anywhere under the workspace. To ensure we’re validating the skill’s required output directory (<workspace>-azure/) and not an accidentally-written file in the source tree, scope these globs to **/*-azure/... like the other migration assertions.
      - type: file-exists
        config:
          path: "**/migration-status.md"
      - type: file-exists
  • Files reviewed: 5/5 changed files
  • Comments generated: 2
  • Review effort level: Lite

Comment thread evals/azure-skills/azure-cloud-migrate/eval.yaml
Comment thread .github/workflows/test-all-integration.yml Outdated
msalaman
msalaman previously approved these changes Aug 5, 2026
@JasonYeMSFT
JasonYeMSFT (JasonYeMSFT) merged commit c817c00 into microsoft:main Aug 5, 2026
12 checks passed
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