Evidence & release validation

Inspect a real comparison#

Our public comparison shows an original test class and its protected counterpart recovered with the same decompiler. You can switch between them, jump to the first or last excerpt, and inspect the complete protected class. The sample records file hashes to keep the published artifacts identifiable.

Use this sample to examine the representation of one protected build. For a release decision, assess the selected configuration alongside compatibility and runtime results from your own application.

Release checks that matter#

• Start the application with JVM verification enabled in its supported environment.
• Compare expected outputs, persistent data and exception behaviour with the original.
• Exercise reflection, serialization, plugin loading and integrations.
• Measure important user workflows and check the protected artifact on a clean deployment target.

Acceptance criteria#

Complexer includes focused tests for transformation behaviour, runtime helpers and execution modes. Your release checks extend that verification to the frameworks, data and deployment environments your application uses.

The protected build, its agreed configuration and its acceptance checks form the release decision. If a check fails, preserve the inputs and contact the team before distributing that build.