By: Alan Page, QA Director, Unity Technologies.
As presented at Spring OnlineTestConf, June13-14 2017
We’ve all heard this story before. “Testers need to be more technical”. The problem with that statement is that too many people read that as, “Testers need to code”. While learning to code or learning to automate can be helpful for a testers growth, there are many, many other (and often, more effective) ways to “be technical” – and valuable, as a tester without writing code.
In this session, long-time test specialist Alan Page rants a bit about the subject, and then shares several real examples of practical tools, techniques, and approaches that will help anyone become a more “technical” tester.
Do you need to call
PrepareMagic here too?
Are there other types of
Why 42? What does it
Myth: Knowing how code works distracts you from testing
Fact: Use knowledge of code to design better tests
Myth: Coding is hard - leave it to the developers
Fact: Yes, coding is hard. But the harder problems to solve
are testing challenges
Myth: Too much coding leaves little time for testing
Fact: Too much of the wrong coding leaves little time for
Big List o Naughty Strings
Other github resources
Keys to being “Technical”
Learn, learn, learn
Frequently experiment with different tools
Find out which tools your teammates and friends are using
Learn how (and when) to apply these tools to make your
testing (and your team) more efficient
Tools, skills, and techniques
are all essential to your