← All courses

Testing in Software Engineering

Why tests actually pay off, the different kinds worth writing, and the habits — TDD, coverage, flaky-test fixes, CI — that keep a suite trustworthy.

testingsoftware-engineeringqualitybeginner

Get Yaaddi on Google Play Free. Install the app, then add this course from its Course Library.

33decks
34main cards
170practice cards
0%with images
v1.1.5version

Card type mix

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
  33. Recap: Key Terms

Example cards

multiple choice

What do tests catch early?

  • Mistakes
  • Feature ideas
  • Meeting notes
multiple choice

Where is a bug cheapest to fix?

  • Before shipping
  • In prod
  • Later

Latest: Haiku review fixes: corrected factual errors and cards that did not match what their lesson teaches.