// Run project tests using Maven (mvn). Use when the user asks to run tests.
Interactive wizard that walks service teams through creating a package-specific skill for their Azure SDK package. Scans the package, detects customization patterns, scaffolds a SKILL.md with references, validates with vally lint, and registers in find-package-skill. WHEN: create package skill; add service skill; bootstrap skill for package; new package skill; skill for my SDK package; write skill for search; write skill for cosmos.
**UTILITY SKILL** — Must be consulted before making any changes to packages under sdk/. Provides package-specific domain knowledge that prevents common mistakes. WHEN: add feature to package; fix bug in package; modify package code; regenerate from typespec; change client library.
Generate code from TypeSpec via tsp-client (update, sync, generate). Requires a tsp-location.yaml in the current working directory. Supports updating the commit hash before running.
Suppress generated Java classes that duplicate openai-java models, using @@alternateType in TypeSpec and manual serialization bridges. Use after dup-classes has identified actionable duplicates.
Verify whether generated Java classes duplicate openai-java models by comparing fields/types (names may differ). Use when checking for duplicate model coverage.
Interact with GitHub using the `gh` CLI. Use `gh issue`, `gh pr`, `gh run`, and `gh api` for issues, PRs, CI runs, and advanced queries.
| name | run-tests |
| description | Run project tests using Maven (mvn). Use when the user asks to run tests. |
Use Maven (mvn) to run tests. Confirm you are in a directory with a pom.xml (project root or module root).
mvn test
mvn -pl <module> -am test
mvn -Dtest=MyTest test
mvn -Dtest=MyTest#myMethod test
If the user asks for live/record/playback, set the env var for the command:
$env:AZURE_TEST_MODE = "LIVE"
mvn test
Tests often require environment variables with connection strings, keys, or other secrets. If another skill or tool for loading secrets or work resources is available, consult the user and use it. Otherwise, ask the user to provide the required environment variables manually. To discover which variables are needed, search for classes named *ClientTestBase in the test sources — these typically define the expected environment variable names.
pom.xml). If not, ask for the correct path.mvn "-Dtest=<TestClass>" test. Only add flags if something fails.-Dtest=<pattern>.-pl <module> -am test.Apply these only if the simple mvn test command fails with the specific error described:
-Dbuildhelper.addtestsource.skip=true -Dbuildhelper.addtestresource.skip=trueokio module issues): add -Dsurefire.useModulePath=false-Denforcer.skip=true -Dcodesnippet.skip=true -Dcheckstyle.skip=true$env:AZURE_TEST_HTTP_CLIENTS = "okhttp"SSLHandshakeException, unable to find valid certification path to requested target): the JVM's trust store is missing the corporate root CA. On Windows, add -Djavax.net.ssl.trustStoreType=WINDOWS-ROOT to use the Windows certificate store. On Linux/macOS, the corporate root CA must be imported into the JVM trust store (or configure a custom one via -Djavax.net.ssl.trustStore / -Djavax.net.ssl.trustStorePassword). This is common on corporate networks with proxy/firewall TLS interception.Do NOT preemptively add all these flags. Start simple and escalate only on failure.