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

Comments

  1. Congrats on being elected a board member. Really looking forward to working with you James!

    ReplyDelete

Post a Comment

Popular posts from this blog

Can Code, Can't Code, Is Useful

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-- "If testers can’t code, they’re of no use to us" My first reaction is to wonder what you expect from your testers. I am immediately interested in your working context and the way

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 answer would be almost meaningless and certa

Not Strictly for the Birds

  One of my chores takes me outside early in the morning and, if I time it right, I get to hear a charming chorus of birdsong from the trees in the gardens down our road, a relaxing layered soundscape of tuneful calls, chatter, and chirrupping. Interestingly, although I can tell from the number and variety of trills that there must be a large number of birds around, they are tricky to spot. I have found that by staring loosely at something, such as the silhouette of a tree's crown against the slowly brightening sky, I see more birds out of the corner of my eye than if I scan to look for them. The reason seems to be that my peripheral vision picks up movement against the wider background that direct inspection can miss. An optometrist I am not, but I do find myself staring at data a great deal, seeking relationships, patterns, or gaps. I idly wondered whether, if I filled my visual field with data, I might be able to exploit my peripheral vision in that quest. I have a wide monito

Postman Curlections

My team has been building a new service over the last few months. Until recently all the data it needs has been ingested at startup and our focus has been on the logic that processes the data, architecture, and infrastructure. This week we introduced a couple of new endpoints that enable the creation (through an HTTP POST) and update (PUT) of the fundamental data type (we call it a definition ) that the service operates on. I picked up the task of smoke testing the first implementations. I started out by asking the system under test to show me what it can do by using Postman to submit requests and inspecting the results. It was the kinds of things you'd imagine, including: submit some definitions (of various structure, size, intent, name, identifiers, etc) resubmit the same definitions (identical, sharing keys, with variations, etc) retrieve the submitted definitions (using whatever endpoints exist to show some view of them) compare definitions I submitted fro

Testers are Gate-Crashers

  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-- "Testers are the gatekeepers of quality" Instinctively I don't like the sound of that, but I wonder what you mean by it. Perhaps one or more of these? Testers set the quality sta

Vanilla Flavour Testing

I have been pairing with a new developer colleague recently. In our last session he asked me "is this normal testing?" saying that he'd never seen anything like it anywhere else that he'd worked. We finished the task we were on and then chatted about his question for a few minutes. This is a short summary of what I said. I would describe myself as context-driven . I don't take the same approach to testing every time, except in a meta way. I try to understand the important questions, who they are important to, and what the constraints on the work are. With that knowledge I look for productive, pragmatic, ways to explore whatever we're looking at to uncover valuable information or find a way to move on. I write test notes as I work in a format that I have found to be useful to me, colleagues, and stakeholders. For me, the notes should clearly state the mission and give a tl;dr summary of the findings and I like them to be public while I'm working not just w

Build Quality

  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-- "When the build is green, the product is of sufficient quality to release" An interesting take, and one I wouldn't agree with in general. That surprises you? Well, ho

Make, Fix, and Test

A few weeks ago, in A Good Tester is All Over the Place , Joep Schuurkes described a model of testing work based on three axes: do testing yourself or support testing by others be embedded in a team or be part of a separate team do your job or improve the system It resonated with me and the other testers I shared it with at work, and it resurfaced in my mind while I was reflecting on some of the tasks I've picked up recently and what they have involved, at least in the way I've chosen to address them. Here's three examples: Documentation Generation We have an internal tool that generates documentation in Confluence by extracting and combining images and text from a handful of sources. Although useful, it ran very slowly or not at all so one of the developers performed major surgery on it. Up to that point, I had never taken much interest in the tool and I could have safely ignored this piece of work too because it would have been tested by

The Best Laid Test Plans

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-- "What's the best format for a test plan?" I'll side-step the conversation about what a test plan is and just say that the format you should use is one that works for you, your coll

Test Now

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-- "When is the best time to test?" Twenty posts in , I hope you're not expecting an answer without nuance? You are? Well, I'll do my best. For me, the best time to test is when there