We hear a lot these days about how testers should learn to code, become more technical, and have more development orientated skills. Unless you came into software testing as a ‘burnt out’ developer, it is unlikely that you have coding skills, or a deep understanding of the technical ins and outs of your current systems landscape.
What can you do about it? Is programming hard? How can you learn to code, gain the benefits and still master your current workload, which keeps on relentlessly increasing?
This workshop will show you how easy it actually is, as a tester, to learn how to program. The hard part, as always, is how to start. We will start with 3 simple steps and get you up and running with Python. You will write the simplest “Hello World” program. However, we will not stop there. We will then explore the ‘next steps’, and give you the confidence to write more complex programs.
Sound great, but when you are back in the office, sitting in front of a blank screen, doing this on your own will suddenly get much harder. To combat that we will arm you with some of the most useful on-line information available. Someone, somewhere on the planet, has already found the answer to your problem, and most likely created a YouTube video showing you how!
As a Tester you know that just writing code is not enough. It has to be shown to work. So not only will we write some code, we will ‘Test’ it as well. To make this even more enjoyable, together we will write programs to control a simple USB Robotic Arm, connected to a Raspberry Pi computer, on which we will run and ‘Test’ our code. We Testers can have fun too!
We will conclude by drawing up a personal development plan for how you can continue to develop your Programming skills, and how you can deploy them back in the office.
To participate it is highly recommended that you bring along a laptop with Wi-Fi that you can; download to, install software on, and edit the path variable. (If you can’t download and install software, i.e. your machine is a secure build, you will still be able to write code in text files that may be transferred to another machine for compilation and running.)
Each journey starts with a single step. Let me help you take your first programming steps today.
(Please note: Due to the limitations of this Server, .py extension files can not be served direct. After opening, whilst saving the file, remove the .txt E.g. Exercise1.py.txt is saved as Exercise1.py)
1. Belgium Testing Days, Bruges, Mar 2014. (Workshop)
2. TMF Summit, London, Apr. 2014. (½ Day Workshop)
3. Czech Test, Prague, Jun. 2014. (Tutorial)
4. Agile Testing Days, Potsdam, Nov. 2014. (Workshop)
5. EuroSTAR, Dublin. Nov. 2014. (Workshop)
6. BCS SIGiST, London, Dec. 2014. (½ Day Workshop)
7. EuroSTAR Webinar, Sep. 2015.
A blog post telling the story of the workshops can be read here http://badgerscroft.com/home/a-year-in-the-life-of-programming-for-testers/.
This session was developed jointly with my good friend Phillip Isles. We co-presented all of the workshops, except for the Czech Test Tutorial.
Phill and I co-wrote the Programming For Testers paper which was nominated for EuroSTAR 2014 best paper.