Your browser is blocking local storage, so your progress will be lost when you close or reload this page.

Build confidence in your code and report defects so others can act on them.

Topics

• Why Testing MattersExpected level: Awareness

  Understand the quality, confidence, and maintainability benefits.

  Not reviewed
• Unit TestingExpected level: Proficient

  Verify individual components in isolation.

  Not reviewed
• Defect ReportingExpected level: Proficient

  Document bugs clearly and reproducibly.

  Not reviewed
• Integration TestingExpected level: Working

  Verify components working together.

  Not reviewed
• Test Data ManagementExpected level: Working

  Create predictable and repeatable test scenarios.

  Not reviewed
• Manual Testing TechniquesExpected level: Working

  Learn exploratory and structured testing approaches.

  Not reviewed
• Test Automation PrinciplesExpected level: Awareness

  Understand where automation creates value and where it does not.

  Not reviewed

Self-assessment

You should be able to do each of these without help.

• Write and run a simple unit test. It should have a clear name, one thing to check, and fail when the code under test is broken.Related: Unit Testing
• Explain the difference between a unit test and an integration test. Give an example of a problem that only the integration test would catch.Related: Unit Testing, Integration Testing
• Write a bug report that someone else can reproduce. Include the steps, expected and actual results, and the version or environment you used.Related: Defect Reporting, Reproducing Bugs
• Test a feature beyond the happy path. Try a value at each side of a limit, an unusual input and an action out of order, and write down what you found.Related: Manual Testing Techniques
• Give each test the data it needs so the tests pass in any order. Explain why real production data must not be copied into a test environment.Related: Test Data Management