Testing in Software Engineering

Card type mix

• multiple choice: 69
• select blank: 48
• true false: 32
• multi select: 30
• order: 8
• match pairs: 7

What's covered

1. What Testing Actually Buys You
2. The Real Cost of Not Testing
3. Unit Tests
4. Integration Tests
5. End-to-End Tests
6. Balancing the Pyramid
7. Arrange, Act, Assert
8. What Makes a Test "Good"
9. Naming Tests So They Explain Themselves
10. Choosing the Right Assertion
11. Mocks, Stubs, Fakes, and Spies
12. When Mocking Helps, and When It Hurts
13. What Code Coverage Really Measures
14. Testing Edge Cases and Boundaries
15. Testing Failure Paths, Not Just Success
16. Red, Green, Refactor
17. What TDD Is Actually Good and Bad At
18. Testing Against a Real Database
19. Testing HTTP APIs
20. Contract Testing Between Services
21. Browser-Driven End-to-End Tests
22. Flaky Tests: Causes and Fixes
23. Performance and Load Testing
24. Basic Security Testing
25. Basic Accessibility Testing
26. Regression Testing
27. Running Tests in CI/CD
28. Managing Test Data
29. Writing a Test With Every Bug Fix
30. Property-Based Testing
31. Mutation Testing
32. When Not to Write a Test

Example cards

Latest: Initial release — 32 decks, 226 cards, each pack with a preview card teaching the concept before its graded main card and practice cards.