Skip to content
Skip to contents
Skip to reading controls

Search skills⌘K

Setting the file. One moment.

This file

Type

Size

Lines

Position

microsoft
/
microsoft/azure-skills

Upgrade Success Criteria · Azure Upgrade · microsoft/azure-skills · Skills Docs

Issue No. 23 · Azure Upgrade

↖Back to the cover

Skills · Azure…

38 chapters · 117 min

Chapter 28 · Azure Upgrade

Subchapter 28.17

Upgrade Success Criteria

references/languages/java/rules/upgrade-success-criteria.mdMarkdown686 BView on GitHub

Upgrade Success Criteria (ALL must be met)

Goal: All legacy Azure SDK dependencies (com.microsoft.azure.*) replaced with modern equivalents (com.azure.*).

28Up to chapter 28Azure Upgrade

This file

Number: 28.17
Position: 17 of 30
Type: Markdown
Size: 686 B

Nearby

Previous Upgrade Strategy
Next Upgrade Bom

Source

28.9Com Microsoft Azure Eventprocessorhost

28.10Com Microsoft Azure Management

⋯17 more in the appendix

28.17Upgrade Success Criteria

Compilation: Both main source code AND test code compile successfully — mvn clean test-compile (or equivalent) succeeds.

Test: 100% test pass rate — mvn clean test succeeds. Minimum acceptable: test pass rate ≥ baseline (pre-upgrade pass rate). Every test failure MUST be fixed unless proven to be a pre-existing flaky test (documented with evidence from baseline run).

If any criterion is not met, load ./troubleshooting.md at that point — do NOT stop or defer.

ReferenceUpgrade Strategy ReferenceUpgrade Bom

references/languages/java/rules/upgrade-success-criteria.md

(opens in a new tab)

Raw file(opens in a new tab)

microsoft/azure-skills(opens in a new tab)