server-testing

To write integration tests using Vitest, adopt a fixture-first approach to create reproducible scenarios and use oRPC's call() function to invoke routers with type safety. This method validates end-to-end behavior across routers, services, and models.

The best way to structure Vitest test suites is by prioritizing integration tests for features and reserving unit tests for utilities. You should enforce clear test organization with strict isolation and cleanup to maintain reliable end-to-end server behavior validation.

An "accessed before declaration" error in Vitest indicates a bug in the code being tested, not the test itself. You should debug the underlying server code implementation rather than inspecting your test assertions or test organization for the failure.

Yes, you can use Vitest to debug server test failures by running the suite locally and inspecting integration fixtures. This workflow helps diagnose errors in the tested code and validates end-to-end behavior using reproducible test scenarios.

You should use integration tests for server features like routers, services, and models, and reserve unit tests only for testing utilities and helpers. This ensures comprehensive validation of end-to-end behavior while keeping isolated logic tests maintainable.