Recap Of WHaTDa And QA Or The Highway

Monday and Tuesday of this week (02/16 and 02/17/2015) had me in Columbus, Ohio for the Workshop on Teaching Test Design and QA Or The Highway. QA Or The Highway is a regional conference designed for software testers. This is the second running, and the second time it has sold out. This time to a bigger crowd than last year.

QA Or The Highway was great again this year. I didn’t attend a whole lot of track sessions, but the ones I did get to were high quality. Joe Ours puts on a good conference.

I did speak at the conference this year which was different from last. I did a talk on testing APIs that included and intro to REST, information on the testing VS checking dilemma, and a live demo with some code I wrote using frisbyjs. Public speaking is a new craft for me, and I’m growing into is and learning from others. Overall, I feel like it went pretty well.

WHaTDa was a one day workshop focused on teaching test design. It reminded me a lot of WHOSE, that is a good thing. We started the workshop at 9am with introductions; a little about who we were, what we were working on, and how we were planning to contribute to the workshop.

The goal, as with most Excelon Development workshops was to produce something useful to the testing community by the end of the day. Usually about halfway into the day, I start getting the feeling that producing something quickly is completely impossible.

After lunch, we split into groups and focused on an exercise we wanted to build and contribute to the wider testing community. I paired, or maybe grouped is a better word, up with Paul Harju, Megan Studzenski, and Dwayne Green.

A new Test Challenge

The 4 of us built something, and we hope it is useful to you.

We build a testing exercise based on a program that determines whether the text you entered into a field is a palindrome or not. It sounds simple, and it is, but there are a number of ways you can frame this simple program into a test exercise.

Here is the Palindrome Challenge. Feel free to use it however you like with credit to the authors.

Here are some framing examples you can use. This is what we came up with during the workshop, there are of course many other ways you can run the challenge.

Framing
For the person giving the challenge: you have to address what the scope of the exercise should be.

Here is one possibility:
1 – Design a test strategy / how would you test this (actually write the strategy down)
2 – Test for a couple of minutes using strategy
3 – What did you find? Did the stuff you found matter? Why?
4 – If you had more time, what tests would you run?
5 – Debrief

You could also do a survey of test techniques.

— Domain
— Function
— Risk
— Load
— Security

Maybe run the exercise a couple times, and see how the test strategy differs based on the identified technique.

Seeding test ideas:
I know there is a bug in X area, how would you test for that?

Megan’s Gambit:
For any given exercise, you can make another exercise by having the student identify what they were doing and why.

Test exercises are everywhere, framing and scoping are the hard part.

Have fun!

I’m speaking at CAST2014

There it is, I’ll be speaking at CAST2014 in NYC this year. I’ve mentioned on twitter that I was accepted to speak but haven’t actually written about it yet.

2014_CAST_Banner

Most simplistic measures for software productivity and quality fail, for reasons you don’t need a conference talk to explain. The problem is how to do better than that – how to “plus one” software measurement, or, at least, to choose measures and frame them in a way that will do more good than harm. Studying a little social science, specifically how social scientists do qualitative research, and measurement problems can help. Justin will talk about the development of qualitative research as a field of study, common problems with measurement in the software world, and some ideas from Lean. You will take back some tools to help you tell a more meaningful story to your business.

I’m in the session group before the last keynote on the last day. This feels a little ominous. If you include the tutorials, and TestRetreat before that, CAST is an intense 5 day marathon of deep discussions on testing and for me a bit of introspection. I will have to be sure to reserve some energy for the talk, especially since this is my first at a real conference, especially since I will be live cast over youtube. I have talks for the local testers group, and facilitated events and whatnot, but for me this is the big-time. CAST is the place.

The theme of this years conference is the art and science of software testing. My talk is themed around measurement. Mainly how it has been traditionally used in our craft, some of how it is used in the social sciences, and a bit on how we can make measurement a useful thing for software delivery and delivering value to the folks that pay for it. Measurement is a difficult problem, but I feel like talking about problems without offering alternate ideas to explore or solid solutions is not all that helpful. I’m hoping we can leave the room with some ideas on making the testers life a little bit better.

Hope to see you there!