Download the PHP package pushinbr/pam-native-testing without Composer
On this page you can find all versions of the php package pushinbr/pam-native-testing. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package pam-native-testing
Why PAM Native Testing
Fake bridge behavior, assert emitted commands, compare golden images, and fail fast on black or transparent screens. The public API is strictly typed for PHP 8.5; expensive or frame-sensitive work stays in Rust or the platform SDK instead of crossing the application boundary every frame.
| Best for | A focused capability you can add to any PAM Native application |
| Native path | Bridge fakes · Golden comparator · Screen sentinels |
| Application model | Composer package + generated native integration |
| Design rule | Independent module; no feed, vertical, or application template bundled |
What you can build
- Unit tests for components and plugins
- Golden visual regression suites
- CI certification of native event and bridge contracts
Quick start
Already have a PAM Native project? Add only this capability:
New to PAM? Follow the five-minute PAM Native setup once, then return here. Your application stays a normal Composer project with a committed lockfile.
See it in action
Deterministic, strict bridge testing for PAM Native applications and plugins.
Responses can be immediate or deferred. Unstubbed calls fail immediately, and
assertSatisfied() detects unused responses and unflushed completions.
Visual certification is deterministic and framework-independent: provide the RGBA pixels captured by Android or iOS, reject black/transparent launch frames, and compare the result with a golden image using explicit channel and changed-pixel tolerances.
What installation does
pam composer require pushinbr/pam-native-testing installs the package through the project's normal composer.json and composer.lock. Run pam doctor --fix afterward to validate the environment and regenerate native integration when required.
Use pam packages to inspect direct installed Composer dependencies and pam composer remove pushinbr/pam-native-testing to uninstall the capability.
API guide
| API | Responsibility |
|---|---|
NativeTestHarness |
Install and remove the fake native-module transport. |
FakeNativeModuleTransport |
Stub success/failure, record calls, defer responses, and assert completion. |
DispatchMode |
Choose immediate or deferred callback execution. |
RecordedModuleCall |
Inspect exact module, method, and payload calls. |
StubbedModuleResponse |
Describe deterministic native results. |
PixelBuffer |
Validate a platform-neutral RGBA screenshot contract. |
ScreenHealth |
Detect black and transparent startup frames. |
GoldenComparator / VisualDiff |
Certify screenshots with measurable tolerances. |
All coded states, kinds, and variants are sequential integer-backed enums. Use enum cases in application code; do not depend on raw wire numbers.
Production checklist
- Uninstall the harness during test teardown.
- Fail every unstubbed native call so tests cannot pass accidentally.
- Call
assertSatisfied()to catch unused responses and pending completions. - Run
pam doctor,pam test, and a signed release build on every supported platform. - Exercise denial, cancellation, backgrounding, process restart, and offline behavior before release.
Troubleshooting
- A test hangs: flush deferred responses or change the dispatch mode.
- An assertion sees extra calls: reset or reinstall the harness per test.
- Production transport leaks between tests: enforce teardown even after failures.
- Native integration is stale: run
pam doctor --fix, rebuild the native host, and inspect the first reported diagnostic.
Compatibility and support
This package targets PAM Native 0.8.x, PHP 8.5, Android API 26+, and iOS 15+ unless a platform-specific section above states a stricter requirement. Platform SDKs, credentials, entitlements, physical hardware, and store configuration remain application responsibilities.
Security vulnerabilities should be reported through the repository security policy or GitHub private vulnerability reporting, not a public issue.
