Skip to main content

First AST the Post



A few months ago I was asked if I'd consider standing for the board of the Association for Software Testing. After giving it a lot of thought, and talking to some people, I decided that I probably did have something to offer, even if it's only the perspective of a relative outsider.

Last week, at CAST 2019 the voting results were announced ... and I'm in!

For the record, then, here's my answers to the election questionnaire.

Q1: Why are you an AST Member?

When I first became a tester I sought out resources to help me learn what testing was. The first book I bought was Lessons Learned in Software Testing and I found that the way it described testing was the way I naturally wanted to test. I researched the authors and their other work which led me to Rapid Software Testing, joining AST, and completing the BBST Foundations course.

I remain a member of AST because of its integrity, its dedication to the testing craft, and its commitment to a strong code of ethical conduct for testing.

The other people I know who are members of AST are, like me, passionate about testing. Sadly, not everyone I know who is passionate about testing thinks the AST is relevant to them.

Q2: How do you intend to promote diversity within the AST? How could AST promote diversity, of all kinds, within our own organization and within the wider testing and technology communities?

The AST’s code of ethics expects its members to respect diversity of cultures and not to discriminate on the basis of race, sex, religion, age, disability, national origin and so on. From the outside, taking the speakers at CAST 2019 as an example, the organisation appears to be demonstrating that it doesn’t believe older white men are the only people who have something useful to say about testing. 
I’d try to promote diversity in and by the AST by encouraging it to seek out people who do not already engage with it and find ways to help them to engage. This might be by making AST relevant to them, by moving AST geographically closer to them, by making AST financially accessible to them, or something else.

Q3: What do you think the AST board has historically done well, and what do you think needs to change?

With only a small number of volunteer staff, I think the board has done well to keep the organisation running, grow and extend its conferences and webinars, and maintain a high level of commitment to testing as a craft and high-quality testing education. 
A significant challenge for AST is that it can seem dry, academic, and a bit dated. Worse, for me, it’s not at all obvious what AST think the point of being a member of AST is.

Q4: If you are elected to serve on the board, what is your vision for the future of AST and what do you hope to accomplish as part of the board?

I’d like to see the passion and dedication that the AST has for testing be more visible and be expressed in more accessible ways. Working out how it wants to coexist with other organisations in the testing space is key. 
Simon Sinek suggests that projects should start with the why and I’ve found that to be good advice in software and other projects. I’d encourage AST to understand why it exists before it starts to make any changes. 
Part of that reflection must include an acknowledgement of the current context where there are test conferences popping up all over the place and groups such as the Ministry of Testing doing a brilliant job of promoting testing.

Q5: Many people come to be AST Board of Directors candidates through a long history of community involvement ... Please describe any current initiatives you participate in that might affect your ability to serve on the AST board, and serve the AST membership

Once or twice a year I help to organise CEWT, the Cambridge Exploratory Workshop on Testing, a small peer conference for the testing community in Cambridge, UK. I regularly attend and support the Cambridge Tester Meetup and its sister Testing Clinic, and I blog regularly at Hiccupps
I don’t believe that these activities will get in the way of AST business.

Q6: What is your vision for the future of AST’s training program?

When I talk to people about the AST’s training program they refer to its depth, breadth, and quality … and also to it being a really significant commitment of both time and effort. My own experience of BBST left me with a similar perspective. I’d add that having a cohort studying the same content together over a constrained time, with dedicated and knowledgeable instructors, is a great motivation to learn and an aid to learning well. It makes BBST stand out from other online learning. 
It isn’t cheap to create training this valued and valuable — and as important to the reputation of AST — so alterations or extensions would need to be carefully considered. I’d want to understand where the AST thinks its niche is (see previous answer) and then align the training program with that.

Q7: (Optional) Would you like to provide a short (250-400 word) introduction to go on your candidate page?

James is one of the founders of Linguamatics, the world leader in innovative natural language-based text mining, and over the years he’s had many roles in the company including web site admin, tech support, and dev manager. He is currently the test manager, a position in which he strives to provide an environment where his testers have an opportunity to do their best work. 
He organises CEWT, the Cambridge Exploratory Workshop on Testing, which has covered topics such as testing ideas, when testing went wrong, why we test, and the values of both testing practice and testing theory. He’s active in the Cambridge testing community, regularly attending, presenting, and promoting its activities.
At EuroSTAR 2015, he won the best paper prize for his talk and essay Your Testing is a Joke, on the relationship between testing and humour. He’s also spoken at UKSTAR 2017, where he described his personal definition of testing and how he arrived at it, and Softtest 2018, about the two-way benefits of testers getting involved in customer support, a topic also covered in his Ministry of Testing ebook, When Support Calls
He’s on Twitter as @qahiccupps and blogs at Hiccupps.
Image: Maria Kedemo

Popular posts from this blog

Meet Me Halfway?

  The Association for Software Testing is crowd-sourcing a book,  Navigating the World as a Context-Driven Tester , which aims to provide  responses to common questions and statements about testing from a  context-driven perspective . It's being edited by  Lee Hawkins  who is  posing questions on  Twitter ,   LinkedIn , Mastodon , Slack , and the AST  mailing list  and then collating the replies, focusing on practice over theory. I've decided to  contribute  by answering briefly, and without a lot of editing or crafting, by imagining that I'm speaking to someone in software development who's acting in good faith, cares about their work and mine, but doesn't have much visibility of what testing can be. Perhaps you'd like to join me?   --00-- "Stop answering my questions with questions." Sure, I can do that. In return, please stop asking me questions so open to interpretation that any answ...

How do I Test AI?

  Recently a few people have asked me how I test AI. I'm happy to share my experiences, but I frame the question more broadly, perhaps something like this: what kinds of things do I consider when testing systems with artificial intelligence components .  I freestyled liberally the first time I answered but when the question came up again I thought I'd write a few bullets to help me remember key things. This post is the latest iteration of that list. Caveats: I'm not an expert; what you see below is a reminder of things to pick up on during conversations so it's quite minimal; it's also messy; it's absolutely not a guide or a set of best practices; each point should be applied in context; the categories are very rough; it's certainly not complete.  Also note that I work with teams who really know what they're doing on the domain, tech, and medical safety fronts and some of the things listed here are things they'd typically do some or all of. Testing ...

The Best Programmer Dan Knows

  I was pairing with my friend Vernon at work last week, on a tool I've been developing. He was smiling broadly as I talked him through what I'd done because we've been here before. The tool facilitates a task that's time-consuming, inefficient, error-prone, tiresome, and important to get right. Vern knows that those kinds of factors trigger me to change or build something, and that's why he was struggling not to laugh out loud. He held himself together and asked a bunch of sensible questions about the need, the desired outcome, and the approach I'd taken. Then he mentioned a talk by Daniel Terhorst-North, called The Best Programmer I Know, and said that much of it paralleled what he sees me doing. It was my turn to laugh then, because I am not a good programmer, and I thought he knew that already. What I do accept, though, is that I am focussed on the value that programs can give, and getting some of that value as early as possible. He sent me a link to the ta...

Notes on Testing Notes

Ben Dowen pinged me and others on Twitter last week , asking for "a nice concise resource to link to for a blog post - about taking good Testing notes." I didn't have one so I thought I'd write a few words on how I'm doing it at the moment for my work at Ada Health, alongside Ben. You may have read previously that I use a script to upload Markdown-based text files to Confluence . Here's the template that I start from: # Date + Title # Mission # Summary WIP! # Notes Then I fill out what I plan to do. The Mission can be as high or low level as I want it to be. Sometimes, if deeper context might be valuable I'll add a Background subsection to it. I don't fill in the Summary section until the end. It's a high-level overview of what I did, what I found, risks identified, value provided, and so on. Between the Mission and Summary I hope that a reader can see what I initially intended and what actually...

Reasonable Doubt

In Your job is to deliver code you have proven to work  Simon Willison writes: As software engineers we ... need to deliver code that works — and we need to include proof that it works as well.  He is coming at this from the perspective of LLM-assisted coding, but most of what he says applies in general. I think this is a reasonable consise summary of his requirements for developers: Manual happy paths: get the system into an initial state, exercise the code, check that it has the desired effect on the state. Manual edge cases: no advice given, just a note that skill here is a sign of a senior engineer.  Automated tests: should demonstrate the change like Manual happy paths  but also fail if the change is reverted.  He notes that, even though LLM tooling can write automated tests, it's humans who are accountable for the code and it's on us to "include evidence that it works as it should." Coincidentally, just the week before I read his post I told one of my...

On Herding Cats

Last night I was at the Cambridge Tester meetup for a workshop on leadership. It was a two-parter with Drew Pontikis facilitating conversation about workplace scenarios followed by an AMA with a group of experienced managers. I can't come to work this week, my cat died. Drew opened by asking us what our first thoughts would be as managers on seeing that sentence. Naturally, sadness and sympathy,  followed by a week ? for a cat ? and I only got a day for my gran! Then practicalities such as maybe there's company policy that covers that , and then the acknowledgement that it's contextual: perhaps this was a long-time emotional support animal . Having established that management decisions are a mixture of emotion, logic, and contingency Drew noted that most of us don't get training in management or leadership then split us into small groups and confronted us with three situations to talk through: Setting personal development goals for others. Dropping a clange...

Great Shot, Kid

This week I've been playing with altwalker , a model-based testing tool. To get the hang of it, I attempted to build a very simple model of a workflow that is supported by the service my team owns. Hacking away at the example code, and looking frequently at the docs, I was able to get up and running in a few hours, creating: a basic model: nodes for system states, edges for operations simple assertions: mainly consistency checks on the states client: HTTP client to implement the operations against the service's API I configured this so that altwalker will perform a random walk of the model, starting state data is randomised, and the client will choose randomly whenever offered an option. Why so much randomness? Because it means that, over successive runs, more of the infinite space of possible workflow executions will be covered. Once I had that basically working I wrote a shell script that would run this loop a number of times: call altwalker ...

LLEWT 2024

This weekend I was at LLEWT 2024, a peer conference on Anglesey , north Wales, discussing communication. Given the day jobs of the participants, it was no surprise that the experience reports and the conversations that followed them mostly focussed on software development contexts.  Notes from my presentation are in Express, Listen, and Field . I made sketchnotes (below) for each presentation and a mindmap (above) to try to summarise the whole. Without much reflection yet, I guess I would pull these common high-level threads from the day: There are multiple reasons that communication fails  ... like, duh! ... but having multiple strategies for framing a message can help ... and having multiple tactics for delivering a message can help too. Understanding what you want from an interaction is key ... so setting the context to make that more likely is wise ... which might mean meta-conversation, being transparent, or changing your approach...

Bottom-up or Top-down?

The theme at  LLEWT this year was Rules and constraints to ensure better quality.   My experience report concerned a team I'd been on for several years which developed (bottom-up) a set of working practices that we called team agreements.   The agreements survived "natural" variation such as people leaving and joining and even some structural reorganisation which preserved most of the team members but changed the team's responsibilities or merged in a few people from a disbanded team. The agreements did not, however, persist through a significant round of (top-down) redundancies where the team was merged with two others.  I'm interested in thinking about the ways in which constraints on how people work affect the work and whether there are patterns that could help us to apply the right kinds of constraints at times they are likely to be useful.  I'm going to use this post to dump my thoughts. My starting po...

Exploring It!

This week the test team at Linguamatics held our first internal conference. There was no topic, but three broad categories could be seen in the talks and workshops that were given: experience reports, tooling, and alternative perspectives on our work. (The latter included the life cycle of a bug, and psychology in testing.) My contribution was an experience report looking at how I explore both inside and outside of testing. I've tidied up some of my notes from the prep for it below. There are testing skills that I use elsewhere in my life. Or perhaps there are skills from my life that I bring to testing. Maybe I'm so far down life's road that it's hard to tell quite what started where? Maybe I'm naturally this way and becoming a tester with an interest in improvement amped things up? Maybe I've so tangled up my work, life, and hobby that deciding where one starts and another ends is problematic? The answers to those questions is, I think, almost certai...