Test a plugin

Test the plugin's public contract and the complete package that users will install. A successful class-library build alone does not establish runtime compatibility.

Focused checks

• Match manifest/runtime identity and the declared Host API range.
• Verify stable action/signal IDs and typed schemas.
• Run startup, reconnect, cancellation and shutdown without an Editor.
• Test invalid fields, stale resource versions and detached validation without mutation.
• Test serialization and migration of project state.
• Verify transfer analysis, dependencies and rollback.
• Check that settings, events, logs and diagnostics expose no credentials.

Use emulated transports for unavailable services and failure cases. Record real-account/device verification separately; a mock success is not evidence that a production account or hardware is configured.

Sign the final package and verify actual entry/dependency loading before distribution. See Packaging.