vtest-integration-testing

To run integration and acceptance tests with Vitest, navigate to your 'src/' directory and execute 'npm run test:integration'. This initiates the test suite to validate component boundaries and user workflows.

The difference between unit, integration, and acceptance tests lies in scope: unit tests isolate functions, integration tests verify boundaries, and acceptance tests validate end-to-end user workflows. This Skill helps differentiate these levels.

Yes, you need a database for Vitest integration testing when validating real infrastructure. This Skill requires Vitest setup and potentially a Postgres, Prisma, or TypeORM database to test actual boundaries and workflows.

You should use acceptance testing instead of unit testing when you need to validate real-world application workflows and user boundaries. A quick decision guide helps choose the appropriate test type based on infrastructure requirements.

Yes, you can test HTTP clients and boundaries using Vitest. This Skill supports testing of boundaries, user workflows, and fixtures by leveraging actual infrastructure and HTTP clients for comprehensive end-to-end validation.