MB-700 study materials
MB-700 study resources

MB-700: Manage testing

MB-700 · Work through your exam, one topic at a time.

All guide sections

Manage testing

Manage testing (about 10–15%) tests how you plan and govern testing rather than how you author a script. Expect questions on test types and sequencing, the Regression Suite Automation Tool, performance testing, and user acceptance testing.

Test types and sequencing

Unit tests use the SysTest framework. Then come functional testing of configuration and extensions in a sandbox, integration testing with external systems, regression testing, performance testing, UAT, and post-go-live smoke tests. Each requirement in the blueprint should trace to at least one test case.

RSAT

The Regression Suite Automation Tool turns Task Recorder recordings into automated test cases stored in Azure DevOps test plans and executes them against a Tier 2+ environment. It needs an Azure AD app registration, a certificate, and a key vault for secrets. Microsoft's Acceptance Test Library supplies ready-made recordings for standard processes; extend them instead of starting blank.

Performance testing

Start early and test on Tier 2+ multi-box environments, since Tier 1 results are not meaningful. Use the LCS performance tools with PerfSDK, the Data Expansion tool to create realistic volume, and Trace Parser to locate bottlenecks. Compare results against a baseline and an agreed pass threshold.

UAT

Business-owned, scripted from end-to-end process scenarios, with entry and exit criteria plus formal sign-off. The implementation team supports and triages defects; it does not run UAT.

Worked example

A customer on One Version wants confidence before each service update. Reasoning: maintain a prioritized RSAT suite covering critical end-to-end processes, run it in a Tier 2 sandbox against the updated build during the update window, and triage failures before accepting the update. A manual regression pass would not fit the update window repeatedly.

Traps

Performance testing on Tier 1; UAT run by the delivery team; no traceability from blueprint requirements to tests; testing only once the build is complete; ignoring the service update calendar.