# capy-testing
In-process HTTP testing utilities for Capy applications.
Applications normally depend on `capy-framework` as `capy` and use its public facade.
Enable the facade's `testing` dev feature and use the same application factory as
the server: `TestApp::boot(application()).await?`. Boot provisions isolated SQLite,
loads test settings and applies the application's migrations. The builder supports
isolated PostgreSQL and explicit real-rendering mail capture. `app.session()`
manages cookies, CSRF, headers and peer identity; login/logout use the real endpoints.
Factories are application-owned Rust values inserted through a supplied database
or transaction. Job helpers run the application's registered handlers. Call
`app.cleanup().await?` after the test; Drop cleanup is best effort.
`TestApp::new(router)` remains available for callers managing their own services.
See [application testing](https://github.com/capy-rs/capy/blob/main/docs/application-testing.md)
and [factories](https://github.com/capy-rs/capy/blob/main/docs/factories.md).
MIT licensed. See LICENSE. This is an initial developer preview, not a production-readiness claim.