Skip to main content

Vote Testers!

 

The Association for Software Testing board elections are happening shortly. Terms are two years long but staggered so that half of the board is up for re-election every year. I've just finished my first term and I've decided to stand again, for a few reasons.

First, and accuse me of whatever cheesiness you like here, I truly believe in the AST's ethical code and mission:

The Association for Software Testing is dedicated to advancing the understanding of the science and practice of software testing according to Context-Driven principles.

It's important to me that I remain a practitioner of testing, and I roll my expertise and experience into the context when I practice. 

Second, and with another helping from the cheeseboard, the AST is emotionally significant to me. When I started testing it was the organisation that Lessons Learned in Software Testing led me to, and its Black Box Software Testing courses helped to culture and mould my intuitions about testing and how I wanted to test.

Third, and onto the coffee now for the business talk, I feel like I have unfinished work that I want to complete.

Next week there are hustings and the candidates have been asked to provide answers to a handful of questions. I thought I'd publish mine here as I did for a similar set after the 2019 elections.

Diversity

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?

All AST members, including the board, sign up to a code of ethics  which requires us to respect the diversity of cultures, not to discriminate on the basis of race, sex, religion, age, disability, national origin or other factors, and to consider whether the results of our work will be used in socially responsible ways.

When I answered the same question two years ago I said I would "encourage AST 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."  

I think I have been able to work towards that:

Black Box Software Testing

Please share your vision for the future of the AST's BBST program.

The recent move to partner with Altom for the provision of the Community Track of Black Box Software Testing is wonderful for multiple reasons. It brings back together the two major forks of BBST, it clears up the confusing relationship between them, and it provides shared resources for the teaching and maintenance of the materials. 

On top of that, it preserves everything that's great about BBST: the depth, breadth, and quality of the material; the small cohort approach; and the dedicated and knowledgeable instructors. In the immediate future I'd like to see us continue to doing everything we can to help that to work well.

In the longer term there have been conversations around broadening the education offerings from the AST to include, for example, something on exploratory testing or automation. We recently ran a course in partnership with Rob Sabourin and I think more of those kinds of partnerships could work for us, because the cost of creating, running, and maintaining courses is high and we have limited resources.

History

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 extraordinarily well to keep the organisation running.

CAST, our conference, is a significant part of what AST is and is known for, and not having CAST in 2020 was a major setback for us. We redirected our CAST energy into more smaller events and we've put something on every month instead, experimenting with different formats like Fika, a super-short and sweet mini-CAST, and even next week's online hustings for the 2021 elections.

A significant challenge for AST has been that it can seem dry, dated, and distant, and the value of being a member can be unclear. In some respects we shoot ourselves in the foot because, while we are a member organisation, our mission is to promote testing in the world and we've tended to err towards making everything we have available to anyone who is interested.

However, despite that difficulty, I support the policy. I want the AST to make a difference to the world generally, to engage with people outside of our organisation, and to grow the testing craft everywhere.

Future of AST

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?

At the first AST board meeting I attended I presented a paper called Why Be A Member of the AST? In it, I compared the value we offered, how we communicated our value and where, and I started thinking about what our various activities cost us versus the value they brought to us and our membership. 

Together we then worked on being explicit about what the AST stands for, what we think our members want from us, and what we want from our members. 

Those activities naturally exposed places that we thought we could do better but it also helped us to prioritise activities to improve on them.

For the last two years I've been working through tasks from that list, incrementally improving what we do and how how we do it. To give some examples:

The next major task for me is to make the cost of entry to AST more equitable.

For the AST more generally: I think there is a place in the world for a non-profit testing organisation advocating for high-quality, ethical, context-driven testing. We need to find better ways to help our tribe to find us, better ways to communicate what we stand for, why we think it is relevant and valuable, and why it's worth helping us to achieve it.

Conflicts of Interest

Please describe any current initiatives you participate in that might affect your ability to serve on the AST board, and serve the AST membership.
I don't have any.

Support

In what ways have you supported the mission of AST?

In lots of ways! I've mentioned some of the things I've done while on the board already. Here's a few examples of stuff I've done outside of AST that I think align with our mission:

  • I blog weekly (for the last ten years) from a context-driven perspective.
  • I am the organiser of the Cambridge Exploratory Workshop on Testing.
  • I speak about testing at work, in the local community, and at conferences.
  • I strive to demonstrate good work, done ethically, according to context-driven principles.
  • I invest time in helping others to test.
  • I invest time in helping myself to improve my testing.

Image: Wikipedia

Comments

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...

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 ...

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...

Beginning Sketchnoting

In September 2017 I attended  Ian Johnson 's visual note-taking workshop at  DDD East Anglia . For the rest of the day I made sketchnotes, including during Karo Stoltzenburg 's talk on exploratory testing for developers  (sketch below), and since then I've been doing it on a regular basis. Karo recently asked whether I'd do a Team Eating (the Linguamatics brown bag lunch thing) on sketchnoting. I did, and this post captures some of what I said. Beginning sketchnoting, then. There's two sides to that: I still regard myself as a beginner at it, and today I'll give you some encouragement and some tips based on my experience, to begin sketchnoting for yourselves. I spend an enormous amount of time in situations where I find it helpful to take notes: testing, talking to colleagues about a problem, reading, 1-1 meetings, project meetings, workshops, conferences, and, and, and, and I could go on. I've long been interested in the approaches I've evol...

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...

ChatGPTesters

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--  "Why don’t we replace the testers with AI?" We have a good relationship so I feel safe telling you that my instinctive reaction, as a member of the T...

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...

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...

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 gener...

Express, Listen, and Field

Last weekend I participated in the LLandegfan Exploratory Workshop on Testing (LLEWT) 2024, a peer conference in a small parish hall on Anglesey, north Wales. The topic was communication and I shared my sketchnotes and a mind map from the day a few days ago. This post summarises my experience report.  Express, Listen, and Field Just about the most hands-on, practical, and valuable training I have ever done was on assertiveness with a local Cambridge coach, Laura Dain . In it she introduced Express, Listen, and Field (ELF), distilled from her experience across many years in the women’s movement, business, and academia.  ELF: say your key message clearly and calmly, actively listen to the response, and then focus only on what is relevant to your needs. I blogged a little about it back in 2017 and I've been using it ever since. Assertiveness In a previous role, I was the manager of a test team and organised training for the whole ...