What the role requires.
WHAT IS FOUNDATIONAL
Analytical thinking Clear written communication Understanding of how software is built Curiosity
WHY WRITING SPECIFICALLY
Most of a tester's output is written, and an unclear defect report wastes everyone's time.
WHAT TECHNICAL SKILLS MATTER
At least one programming language Version control Interfaces and how they work Databases and querying Command line competence Understanding of networks
WHY QUERYING MATTERS
Verifying what was stored requires reading it directly.
WHAT AUTOMATION REQUIRES
Programming ability, genuinely.
WHY
Test code is code, and poorly written test code becomes unmaintainable faster than production code.
WHAT DOMAIN KNOWLEDGE PROVIDES
The ability to recognise what is wrong, not only what differs from a specification.
WHY THAT MATTERS ENORMOUSLY
Many serious defects are only visible to someone who understands the business.
WHAT TO LEARN ABOUT THE SYSTEM
How it is built Where the risk concentrates What has broken before
WHAT TO DEVELOP OVER TIME
Judgement about where to look.
WHAT SEPARATES EXPERIENCE
Knowing what usually breaks.
