An interesting discussion came up recently on the Ministry of Testing Slack. It’s one that I loved to see because it reminded me of some of the excellent developers I have worked with in the past.
our developers are asking if I could talk to them about tips on testing that they could use in their work, to catch the worst stuff before my testing. I don’t know how to approach this I test user interfaces of consumer websites and apps and don’t code, so that’s where I am coming from. Has anyone ever done talked to developers about something like this?
With follow up information of:
I need to give a stand alone talk about what they can individually do, possibly in projects where I am not even around.
normal thing to talk with the Devs about possible issues and what they could maybe already check
- unit tests
- integration tests
- happy path testing
- some basic tips what to look for e.g. for date field: what happens if you enter a day in the past, today, future
Maybe basic, but I had projects where they obviously didn’t do it: when they think the feature is “done” they should verify it in the demo environment, clicking through it so it does not only “works on my machine”
Maybe do some pair programming sessions where you show them how you test?
Also, when you catch a bug, do the root cause analysis together with the dev so everyone learns from it
I think that checklists are VERY useful. Basic stuff:
- Does the page I’ve created or edited look right
- When I enter expected data, does it save correctly?
- What about unexpected data?
- When I access existing items that are saved do they load correctly?
- When I edit items do they save correctly?
What would you add or expand on in the above suggestions?