Pre-release acceptance checklist

Successful activation is the first check. Verify that real operations are protected and failure and recovery behave as expected.

Use a dedicated test product and license. Complete the real first activation by copying the key into your own app. Automated denial, quota and failure cases can use local fixtures. Record what was actually tested and what remains unverified.

• First activation: paste the key manually, see success and execute a real protected operation.
• Restart: the same user does not re-enter the key; other users cannot reuse that cache.
• Business protection: an ungranted feature cannot execute through a button, shortcut, command or background entry point.
• Network and denials: offline behavior follows the signed policy; protected operations stop after offline expiry or an explicit server denial.
• Devices and seats: test device limits, full floating capacity, normal exit, recovery after a crash and explicit customer transfers.
• Metering and retries: success confirms usage, failure cancels, and settlement retries do not repeat the business operation; crash outcomes can be reconciled.
• Versions and offline files: test permitted and denied versions, response import on the original machine and rejection on another machine when these features apply.
• Release checks: no full keys in logs, no test credentials in the installer, and error screens offer a useful next step while preserving user data.

Verify advanced capabilities only when your product uses them. A basic device-bound product does not need metering, floating seats or version restrictions enabled merely for testing.

Troubleshoot failures by error code · Back to manual integration