Words to a new software QA

We're not after the developers. We're after their code. It's not personal.

If they didn't want us to find the bug, they shouldn't have written it in the first place.

QA starts with the requirements, if those are vague, the result will not be what the customer wants.

Not finding a bug does not prove there are no bugs. It proves you didn't find one right there, at that particular planetary alignment with that precise set of system and environment and time of day and test data.

There is always a bug somewhere.

Learn how to program in the language your developers use. Also learn SQL (Structured Query Language), HTML, CSS, and any other acronyms you hear often.

Your developers are an amazing resource and are usually very helpful when presented with a "Can you please help me..." request.

Keep learning. There is always a new language, or tool, or technique, or platform, or environment, or program.

Get up and walk around often. Drinking large amounts of water will help this. Give your eyes a rest from the screen and go talk to your team.

This entry was posted in Geek/Tech, Humour, QA. Bookmark the permalink.

2 Responses to Words to a new software QA

  1. Paul B. =:o} says:

    All sound wisdom, Ali. =:o}

    It’s this bit that stops me short: “Learn how to program in the language your developers use. Also learn SQL (Structured Query Language), HTML, CSS, and any other acronyms you hear often.”

    I think I *could* have been a really good QA bod, if only technology hadn’t kept on changing faster than I could learn new stuff.

    So now I “debug” the prices and the layout of things on shelves in an IT store, instead. And even with that step-down in requirements, it’s pretty hard to keep up … =:o

  2. Paul B. =:o} says:

    (By “technology”, of course, I really mean “fashions in what technologies people want to be seen using”. =:o? )