Testing

Extension acceptance requires more than a successful JavaScript build. Verify the public definition, the installed package, and the declared musical or file operation.

Static checks

Run the generated type-check and build commands:

npm run check
npm run build

If type checking fails, the package does not satisfy the SDK declarations. If the build fails or does not produce the manifest entry path, Amadeus cannot load the package.

Definition checks

Use .toDef() in unit tests when a test needs to inspect the package definition without registering it. Verify at least:

• stable package and member identifiers;
• expected roles, stages, and order;
• every parameter key, type, default, bound, stage, and cache scope;
• the operations offered by each unit.

Installed smoke test

1. Install the built package in a clean user plugin directory.
2. Open View → Plugins…, reload, and enable it.
3. Confirm its name, version, status, and parameter groups.
4. Exercise the declared operation in a representative project.

For a post-pitch package, test voiced and unvoiced material, confirm that the returned contour remains finite and the same length, and verify that the neutral parameter value leaves the audible result unchanged.

User-result test

Document one condition for which the extension should act and one for which it should remain neutral. Bake both cases. A passing technical check does not prove that the user-visible result matches the package description.