Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Tangible truths about technical testing

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.

  • Login to see the comments

  • Be the first to like this

Tangible truths about technical testing

  1. 1. Tangible Truths About Technical Testing TL;DR Testing is Technical
  2. 2. Let’s talk about being “technical”...
  3. 3. ...using the techniques of the craft...
  4. 4. Accelerate the achievement of shippable quality
  5. 5. Some rights reserved - Stacy Jensen
  6. 6. Some rights reserved - Rino Peroni
  7. 7. Technical Testing
  8. 8. “Technical” == “coding”
  9. 9. “coding” == “automation”
  10. 10. “automation” == “UI Automation”
  11. 11.
  12. 12.
  13. 13. Stop thinking that technical means coding
  14. 14. Stop worrying about being technical
  15. 15. Instead, think about being valuable
  16. 16. Of course, if you’re more technical, you’re be more valuable...
  17. 17. Accelerate the achievement of shippable quality
  18. 18. Augmentation over automation
  19. 19. “We can’t change it” “It’s just the way it works” “It’s management’s fault”
  20. 20. You can change your manager, or you can change your manager. Making change happen is part of being successful in knowledge work.
  21. 21. Alan’s Tips: Do it anyway Experiment Find allies
  22. 22. Reading recommendations:
  23. 23. ...meanwhile, on the topic of Technical Testing...
  24. 24. Filling your technical testing toolbelt
  25. 25. 1. Learn to something about code
  26. 26. Scenario: Every day, I find the latest version of our software, then copy the files to my local machine, then run setup, then start the app so I can do my testing.
  27. 27. Make your testing easier (accelerate your testing)
  28. 28. Read code
  29. 29. Ask Questions Do you need to call PrepareMagic here too? Are there other types of magic? Why 42? What does it mean?
  30. 30. 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 testing
  31. 31. 2. Learn to use tools
  32. 32. Scenario: I need to know how many image requests our web site gets. I need to understand what our app (web or desktop) is doing.
  33. 33. grep F12 Fiddler ( Sysinternals tools ( 2062.aspx)
  34. 34. 3. Learn new ideas
  35. 35. Big List o Naughty Strings Other github resources Also: - Virtualbox - WireMock - JMeter - etc.
  36. 36. Discover what you don’t know you don’t know
  37. 37. 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
  38. 38. Tools, skills, and techniques are all essential to your success
  39. 39. Learn, adapt, and influence.
  40. 40. @alanpage