The talk was recorded on video and will be available later in its recorded format."How would you test a text field" by @maaretp was a great display of methodology and added some pretty useful stuff to my development toolbox. Thank you very much! #Craftconf— Vincent Fahrenholz (@DrearyTown) May 11, 2018
What I find interesting though is the stuff going through my mind post talk, thinking through all the things I want to do differently.
The talk had five sections to it.
- Introducing a common model of assessing testers in job interviews: "How would you test a text field?" and one way of judging the responses
- Testing a text field without functionality
- Testing a text field in product context through UI & filesystem
- Testing a text field in code context through API with automation
- Testing a text field that is more than a text field
- When testing a text field without functionality, get people to generate test ideas to the same functionality with GUI present or API present - focus on what functionality is in which layer
- Visualize test ideas from the group better - use a mindmup. Map them to the four level model of how a tester thinks.
- Teach the model of testing better: I intentionally create first "phases" of idea collection, idea prioritization, and learning from results before selecting or generating a new idea for the next test in the first exercise. Later exercises I allow for prioritized ideas to action, but force discussion on what the test made us learn. When I test, it all mingles.
- Force the focus in code context better to just the text field, blur the frame needed to run things out.