๐Ÿ™ Junior Tester Starter Kit

Junior Tester Starter Kit ๐Ÿž

โ† Back to Kit Home

Junior Tester Starter Kit ๐Ÿž

Welcome! This kit is made for junior software testers โ€” people who are new to testing or in their first year. Most of the kit is for manual testers, but there is also a section for beginners in test automation.

Everything here is written in simple English so it is easy to read, even if English is not your first language.


What is inside?

junior-tester-kit/
โ”œโ”€โ”€ README.md                        โ† You are here
โ”œโ”€โ”€ guides/
โ”‚   โ”œโ”€โ”€ testing-basics.md            โ† What testing is, types of testing, SDLC/STLC
โ”‚   โ”œโ”€โ”€ bug-reporting.md             โ† How to write a great bug report
โ”‚   โ””โ”€โ”€ learning-roadmap.md          โ† 3-month learning plan with free resources
โ”œโ”€โ”€ templates/
โ”‚   โ”œโ”€โ”€ test-case-template.md        โ† Reusable test case template + 3 examples
โ”‚   โ”œโ”€โ”€ bug-report-template.md       โ† Reusable bug report template + 2 examples
โ”‚   โ””โ”€โ”€ test-plan-template.md        โ† Lightweight test plan template
โ”œโ”€โ”€ automation/
โ”‚   โ””โ”€โ”€ starter-scripts.md           โ† Intro to automation + example code
โ””โ”€โ”€ glossary.md                      โ† 40+ testing terms explained in one line each

How to use this kit

  1. New to testing? Start with guides/testing-basics.md. It explains the main ideas.
  2. Need to report a bug? Read guides/bug-reporting.md, then copy the template from templates/bug-report-template.md.
  3. Writing test cases? Copy templates/test-case-template.md and follow the examples.
  4. Planning a test cycle? Use templates/test-plan-template.md.
  5. Want to learn automation? Read automation/starter-scripts.md for simple starting points.
  6. Don't understand a word? Check glossary.md.
  7. Want to grow fast? Follow the 3-month plan in guides/learning-roadmap.md.

The 5 golden rules for junior testers

  1. Ask questions. There are no stupid questions. Asking is faster than guessing.
  2. Write things down. Good notes make good bug reports.
  3. Reproduce before you report. Always try the bug 2โ€“3 times before you write it up.
  4. Be clear, not clever. Simple words help everyone.
  5. Learn a little every day. 30 minutes a day beats 5 hours once a month.

Good luck, and happy testing! ๐ŸŽฏ