Adding Tests to Your Copilot Workspace Project

Most Copilot Workspace projects ship with zero tests. This means every change is a gamble — you might fix one thing and break three others without knowing until a user reports it. Tests are automated checks that verify your app works correctly. They run in seconds and catch bugs before your users do.

Copilot Workspace can generate tests as part of its PRs. Review that generated tests are testing the right thing and are added to the right test file. Ensure your CI pipeline runs all tests on PR branches

Check that tests generated by Copilot Workspace actually test the feature described, not just the code it happened to generate. Look for missing test cases for error paths and edge cases. Verify that existing tests still pass and haven't been unintentionally broken by the generated changes

Unit tests check individual functions in isolation — does this function calculate the right total? Integration tests check that multiple pieces work together — does submitting this form save to the database? End-to-end (E2E) tests simulate a real user — can someone sign up, log in, and complete a purchase? Start with E2E tests for your most critical flows, then add integration tests for your API endpoints.

Set up your tests to run automatically on every code push using GitHub Actions or a similar CI service. This way, you'll know immediately if a change breaks something. A basic CI pipeline runs your tests, checks for TypeScript errors, and builds the project. If any step fails, the push is flagged before it reaches production.