request-factories
phiremock
| request-factories | phiremock | |
|---|---|---|
| 2 | 2 | |
| 591 | 147 | |
| 1.0% | - | |
| 5.0 | 0.0 | |
| 3 months ago | over 1 year ago | |
| PHP | PHP | |
| MIT License | GNU General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
request-factories
- how to fake a response of an external server/api for a laravel feature test?
-
Presenting Request Factories, a package to make request testing even better! (Link in description)
Hi all! Here’s the link: https://github.com/worksome/request-factories I’m pleased to announce the release of “Request Factories by Worksome”, a package designed to make testing requests in Laravel beautiful. No more repeating the same required fields across requests; request factories moves all of that boilerplate to a powerful factory class and allows your tests to stay focused and purposeful. I created an in-depth blog post all about it which you can read here: https://downing.tech/posts/using-request-factories-for-gorgeous-feature-tests Hope you enjoy it. Keep on being awesome!
phiremock
-
how to fake a response of an external server/api for a laravel feature test?
In one symfony project I am working on we are using this phire mock
-
Best practice to stub third party APIs when running Dusk tests or local dev environment.
I've been using phiremock for years to mock API calls from backend, and I would recommend it. You can start the webserver from the Cli and have it being called by your backend, by just switching the base URL to - for instance - localhost:18080 By default it will load all the expectations (mocks) inside a directory, recursively, and propose different matching patterns to send the appropriate response to the request
What are some alternatives?
comments - Native comments for your Laravel application.
PHP-Mock: mocking built-in PHP functions - Mock built-in PHP functions (e.g. time(), exec() or rand())
laravel-messenger - Simple user messaging package for Laravel
Mockery - Mockery is a simple yet flexible PHP mock object framework for use in unit testing with PHPUnit, PHPSpec or any other testing framework. Its core goal is to offer a test double framework with a succinct API capable of clearly defining all possible object operations and interactions using a human readable Domain Specific Language (DSL).
Pest - Pest is an elegant PHP testing Framework with a focus on simplicity, meticulously designed to bring back the joy of testing in PHP.
Codeception - Full-stack testing PHP framework
laravel-package-tools - Tools for creating Laravel packages
guzzler - Supercharge your app or SDK with a testing library specifically for Guzzle
archetype - Edit PHP files programmatically
laravel-optimus - Transform your internal id's to obfuscated integers based on Knuth's integer hash. Laravel wrapper for the Optimus Library by Jens Segers with multiple connections support.
testbench - Laravel Testing Helper for Packages Development