Upgrade to Pro — share decks privately, control downloads, hide ads and more …

The Tester at the Table and the Tester in my Head

The Tester at the Table and the Tester in my Head

Do you want to make an impact? Do you want your work to reach people far and wide? Do you know which of your responsibilities will have this far-reaching impact?

Through 15 years of software development, Adrian P. Dunston has had opportunities to work with dedicated and talented QA professionals. And now he has a little tester in his head.

As the tester at the table, you have an opportunity to set high standards of quality not only in products and processes but in the developers you work with. And by building quality developers, your impact can reach every project and every other developer they work with thereafter. At the very least, you can make life easier on the next poor sap that gets to QA their code.

So how does one go beyond improving products and start improving teams? How do you build up the little testers in their heads? Based on extensive reading and years of working with and without the support of QA professionals, Adrian will show you:

* How to mold quality-minded developers
* How to use repetition and story to get your ideas stuck in their heads
* How to instill habits they can use and take with them
* And why exposure to good QA person can be invaluable to a young developer

Adrian Dunston

November 08, 2018
Tweet

More Decks by Adrian Dunston

Other Decks in Technology

Transcript

  1. @bitcapulet @bitcapulet 64 Nobody will buy half the store. But

    if they do, you'll want your register working.
  2. @bitcapulet @bitcapulet • Prove it. • How do we know

    it's working? • Might be a load-bearing bug. • That's why we have checklists • If it were broken in production, how would we know? • You support me, and I keep you safe. • You explain, I decide. • Don't feed the test-matrix • It's OUR job to make quality software 66
  3. @bitcapulet @bitcapulet 80 First: I lost an argument about risk…

    Then: We all had to stay late when the app exploded.
  4. @bitcapulet @bitcapulet First: A dev told me "works on my

    machine"... Then: I asked him where my environment was different, and he found the bug. 83
  5. @bitcapulet @bitcapulet 132 You support me, and I keep you

    safe. 1. Stick up for me 2. Do fit and finish
  6. @bitcapulet @bitcapulet 139 You support me, and I keep you

    safe. 1. Stick up for me 2. Do fit and finish
  7. @bitcapulet @bitcapulet 150 You support me, and I keep you

    safe. 1. Stick up for me 2. Do fit and finish
  8. @bitcapulet @bitcapulet 167 The question isn't can we afford regression

    testing, it's can we afford to have our users do it? Reframing
  9. @bitcapulet @bitcapulet 169 The question isn't, "Are techniques like this

    sneaky?" It's "How can we make sure we're using our powers for good?"
  10. @bitcapulet @bitcapulet 183 I really think it should stay in

    dev. Would you prefer to try it in production?
  11. @bitcapulet @bitcapulet 185 I know I'm right. Whether you learn

    that the hard way or the easy way doesn't matter to me.
  12. @bitcapulet @bitcapulet 192 Good news: If all goes according to

    plan, developers will start following your advice.
  13. @bitcapulet @bitcapulet 194 Bad news: They will also think it

    was their idea in the first place. They are geniuses, after all.
  14. @bitcapulet @bitcapulet 202 Quality is the hidden ingredient in all

    of our products. But it’s consumed just like everything else. QA professional Mike Baldwin says...
  15. @bitcapulet @bitcapulet 221 QA professional Jenny Bramble says... When you

    walk into a job, there’s a grocery list of stuff that people want you to finish. Look beyond the list. See what's driving the list.
  16. @bitcapulet @bitcapulet 228 1. Repeat yourself 2. make a deal

    3. Argue (correctly) 4. Promote yourself
  17. @bitcapulet @bitcapulet 234 1. Repeat yourself 2. make a deal

    3. Argue (correctly) 4. Promote yourself for the humans!