serverpod-testing

To test Serverpod endpoints with database seeding and rollback, use withServerpod to seed data in setUp blocks and rely on transaction rollback semantics. Configure afterAll or disabled rollback when concurrency requires it to ensure deterministic integration testing.

Yes, you can test authenticated vs unauthenticated behavior deterministically in Serverpod integration tests by using the sessionBuilder.copyWith method to override authentication context within your test cases.

The best way to verify real-time stream delivery in Serverpod tests is to use stream testing utilities like flushEventQueue, which ensures yields are fully executed before assertions are made. This guarantees accurate testing of real-time message delivery.

Yes, you need the generated test tools import to run Serverpod endpoint tests, as it provides the necessary withServerpod sessionBuilder and endpoint configurations to satisfy startup and rollback requirements for reliable execution.

To test Serverpod business logic that is not inside an endpoint, create and pass a Session object directly to your non-endpoint logic. This allows you to leverage full server context including caching and database access during testing.