PHPackages wondernetwork/slim-kernel-testing-harness - PHPackages - PHPackages [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register) 1. [Directory](/) 2. / 3. [Testing & Quality](/categories/testing) 4. / 5. wondernetwork/slim-kernel-testing-harness ActiveLibrary[Testing & Quality](/categories/testing) wondernetwork/slim-kernel-testing-harness ========================================= 1.0.0(7mo ago)05.1k↓53.3%MITPHP >=8.3CI passing Since Nov 12Compare [ Source](https://github.com/WonderNetwork/slim-kernel-testing-harness)[ Packagist](https://packagist.org/packages/wondernetwork/slim-kernel-testing-harness)[ RSS](/packages/wondernetwork-slim-kernel-testing-harness/feed)WikiDiscussions Synced 2d ago READMEChangelog (1)Dependencies (4)Versions (5)Used By (0) Test harness for [SlimKernel](https://github.com/WonderNetwork/slim-kernel) =========================================================================== [](#test-harness-for-slimkernel) Overview -------- [](#overview) The goal of this package is to make writing high-level tests exciting by building sufficient architecture around them, that would make it easy and expressive to build your test cases. Installation ------------ [](#installation) ``` composer require --dev wondernetwork/slim-kernel-testing-harness ``` Core concepts ------------- [](#core-concepts) ### `SlimKernelHttpClient` [](#slimkernelhttpclient) ``` use WonderNetwork\SlimKernelTestingHarness\KernelHttpClient as Core; $httpClient = Core\SlimKernelHttpClient::create($slimApp); ``` This class acts as a HttpClient directing the requests at the provided Slim App, which is at it’s core a Request Handler. The most basic usage is to use one of the convenience methods modeled after HTTP verbs: - `$httpClient->get("/url")` - `$httpClient->head("/url")` - `$httpClient->post("/url", payload: [...])` - `$httpClient->put("/url", payload: [...])` - `$httpClient->patch("/url", payload: [...])` - `$httpClient->delete("/url")` Or a more advanced, by crafting the request manually (or using the provided `RequestBuilder`) and passing it to the `request()` method. Each request is by default expected to succeed, as determined by returning a HTTP status code in the 1xx-3xx range. You can change the behaviour by calling the `withResponseExpectation` method: - `withResponseExpectation(ResponseExpectation::Failure)` — codes greater or equal to 4xx - `withResponseExpectation(ResponseExpectation::Success)` — below 4xx, the default - `withResponseExpectation(ResponseExpectation::None)` — status code assertions disabled *Hint*: when building test cases outside the happy path, such as making sure your authorization mechanism works correctly, you will want to use the `ResponseExpectation::Failure` mode. ### `HttpResponseAssertion` [](#httpresponseassertion) Each `SlimKernelHttpClient` returns a `HttpResponseAssertion`, which helps you make common assertions about the response and access its contents. Example helper methods: - `assertSuccess()` and `assertFailure()` (useful you called with the `ResponseExpectation::None`) - `expectJson()` asserts the response was a valid JSON and return its parsed data - `isSuccessful()` indicates if the response http code is in the 1xx-3xx range - `assertRedirect($to = null)` asserts the response is a redirect and optionally makes sure the `Location` header matches the provided value - `slimErrorPage()` returns an object representing the default Slim error page, so you can make assertions about the thrown exception type or its message The [PSR-7](https://www.php-fig.org/psr/psr-7/) Response object is available as a public `$response` field. For convenience, the calling `SlimKernelHttpClient` is also attached as `$httpClient`. ### Use Cases (`KernelHttpUseCase` trait) [](#use-cases-kernelhttpusecase-trait) To organize your test cases, and make reusable actions, it’s good to organize your sources into use cases. These use cases are an SDK of sorts for your app. They represent an abstraction over your application’s API. Look at the examples: ``` class AdminUseCasesFacade { use KernelHttpClientUseCase; public function listOrders(): OrderListAssertion { return OrderListAssertion::ofJsonResponse( $this->httpClient->json()->get('/api/v1/orders') ); } } class CustomerUseCasesFacade { use KernelHttpClientUseCase; public function makeOrder(string $productId): void { return $this->httpClient->post('/api/v1/orders', ['product' => $productId]); } } ``` The trait is here to provide a couple of convenience methods. Since most of your use cases will only use the `SlimKernelHttpClient` as the entrypoint into your app, this is the only dependency for your use cases. The trait provides the factory method `of($httpClient)`to create an instance, the constructor to store the client in a protected field, and two helper methods to control the response expectation: `expectFailure()` and `noResponseExpectation()` ``` CustomerUseCasesFacade ::of($httpClient) ->expectFailure() ->makeOrder($invalidProductId) ``` ### Assertions (`JsonListResponseAssertion` and others) [](#assertions-jsonlistresponseassertion-and-others) To build a robust test suite, most of your API endpoints will need a custom assertion class (responsible for holding the response data and making assertions on it). One particularly interesting instance of this are assertions about endpoints listing multiple records. Their handling can be made easier by using the `JsonListResponseAssertion`: ``` class OrderListAssertion { use JsonListResponseAssertion; public function first(): OrderItemAssertion { return new OrderItemAssertion($this->items->getFirstItemData()); } } ``` It automatically provides the `ofJsonResponse` factory method, which can directly take the result of a `$httpClient->request()` call. An advanced usage of the assertions and use cases is presented in the [examples](examples) folder. ### Middlewares [](#middlewares) Inputs for a high-level e2e test are such complex and diverse. Different clients craft different payloads, which include: - `JSON` payloads - `multipart/form-data` or `application/x-www-form-urlencoded` payloads - Requests with basic auth, bearer tokens or client certificates - Stateful session cookies or other similar authentication mechanisms It’s challenging to fit all this complexity and provide keep the simple interface such as the `SlimKernelHttpClient` has. The package solves this problem by allowing adding a [PSR-15 middlewares](https://www.php-fig.org/psr/psr-15/)to the client. Two basic ones are built in: - `$httpClient->json()` adds an `Accept` header to indicate json payloads are expected, as well as the `X-Requested-With` header to simulate a browser - `$httpClient->withBaseUrl($url)` will prefix each request url with a given value - use `$httpClient->withMiddleware()` to add a custom one Custom middlewares in combination with different use cases for different clients of your app can be very powerful. You can look at the (example middlewares)\[examples/middlewares\] to a glimpse of how they can be used. ### Health Score 40 — FairBetter than 86% of packages Maintenance62 Regular maintenance activity Popularity23 Limited adoption so far Community9 Small or concentrated contributor base Maturity53 Maturing project, gaining track record Bus Factor1 Top contributor holds 71.4% of commits — single point of failure How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window. **Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores. **Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement. **Maturity (30%)** — Project age, version count, PHP version support, and release stability. ### Release Activity Cadence Unknown Total 1 Last Release 233d ago ### Community Maintainers ![](https://www.gravatar.com/avatar/8572223899390b494d1282b615009bc2eea5ef1cd6bfc22f6e6b175034dadfe0?d=identicon)[mlebkowski](/maintainers/mlebkowski) ![](https://www.gravatar.com/avatar/341a28d185d58818b433a0447f4f97df322bd172f528879d24febfc075df8d35?d=identicon)[preinheimer](/maintainers/preinheimer) --- Top Contributors [![mlebkowski](https://avatars.githubusercontent.com/u/848731?v=4)](https://github.com/mlebkowski "mlebkowski (5 commits)")[![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?v=4)](https://github.com/dependabot[bot] "dependabot[bot] (2 commits)") ### Code Quality TestsPHPUnit Static AnalysisPHPStan Type Coverage Yes ### Embed Badge ![Health badge](/badges/wondernetwork-slim-kernel-testing-harness/health.svg) ``` [![Health](https://phpackages.com/badges/wondernetwork-slim-kernel-testing-harness/health.svg)](https://phpackages.com/packages/wondernetwork-slim-kernel-testing-harness) ``` ### Alternatives [dms/phpunit-arraysubset-asserts This package provides ArraySubset and related asserts once deprecated in PHPUnit 8 14429.2M361](/packages/dms-phpunit-arraysubset-asserts)[gong023/assert_chain enable you to use phpunit assert with method chain 1478.9k3](/packages/gong023-assert-chain) PHPackages © 2026 [Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)