- What does owenvoke/pest-plugin-memory do?
- It is a Pest 1.x plugin that adds memory usage expectations to your test suite. You can assert how much memory a piece of code consumes and catch memory regressions early. It is lightweight and designed to fit Pest's expressive testing style.
- How do I install owenvoke/pest-plugin-memory?
- Install it as a development dependency with Composer using composer require --dev owenvoke/pest-plugin-memory. You should already have Pest 1.x set up in the project. After installation, the plugin's expectations should be available in your Pest tests; check the README for exact usage.
- Does pest-plugin-memory work with Pest 2 or Pest 3?
- The package description explicitly targets Pest 1.x, so it is not intended for Pest 2.x or Pest 3.x. If you are on a newer Pest version, check the repository and Packagist for an updated release or use a maintained alternative. Mixing it with newer Pest versions may cause compatibility issues.
- Is owenvoke/pest-plugin-memory compatible with Laravel?
- It can be used in Laravel applications as long as the project is running Pest 1.x. The plugin is a Pest extension rather than a Laravel package, so it does not add Laravel-specific configuration. Laravel version compatibility therefore depends mainly on your Pest version and PHP environment.
- How do I assert memory usage in a Pest test?
- The plugin adds memory expectations so you can wrap the code you want to measure and assert its memory consumption in a Pest test. The exact expectation names and syntax are defined in the package README. Use those assertions alongside your normal Pest expectations to monitor memory behavior.
- Does the plugin require configuration after installation?
- It is described as a simple, lightweight Pest plugin, so it should not need extensive configuration. Pest plugins are generally enabled through Composer installation and Pest's plugin loading. Verify the README for any required setup or minimum Pest version details.
- Can I use pest-plugin-memory in CI to catch memory regressions?
- Yes, memory expectations are well suited to CI because they turn memory consumption into test assertions. If a change causes code to exceed your expected memory threshold, the test can fail and alert you early. Keep thresholds realistic because memory measurements can vary between environments.
- How does pest-plugin-memory measure memory usage?
- The plugin provides memory usage expectations for code executed inside your Pest tests. It is intended for relative regression checks rather than precise profiling of every allocation. For detailed profiling, use dedicated tools like Xdebug, Blackfire, or Laravel Telescope in addition to these assertions.
- Is pest-plugin-memory suitable for production code?
- It is a development and testing dependency, not a production runtime package. You should install it with Composer's --dev flag and keep it out of production deployments. Its assertions belong in your test suite, where they help catch memory regressions before release.
- What should I use if pest-plugin-memory is not maintained for my Pest version?
- First check the GitHub repository and Packagist for newer releases or forks that support your Pest version. If none exist, you can write custom memory assertions in Pest or use a general PHP profiling tool for memory regression checks. For Laravel projects, also consider framework-level debugging and profiling tools.