📚 A is for [...]

A is for Automation

What else springs to mind with A and our software testing career?

[LinkedIn & Twitter versions]

ASSERT, A is for ASSERT(1)
You can tell, can’t you that I am code jockey :slight_smile:

Again
we don’t have enough time for the proper testing AGAIN

A is for Acceptance Criteria.

Capture Acceptance Criteria to define the expected outcome of something to be built (and checked/tested as part of how it’s built). Acceptance Criteria are a good oracle for test ideas, particularly for checking activities and a good starting point for exploring risks via exploratory testing sessions.

A is for Accessibility, an attribute we want the thing to have.

A is also for Anti-intuitive, which I’d swear my career makes the norm.

A is also for Alternative Methods, something we testers are very good at finding.

Abstraction - breaking complex stuff down in manageable and understandable bits

A is for AI generated tests duh!

Assurance - An audit between the end product and requirement analysis.

You ALWAYS have time for “proper” testing. Since testing is potentially infinite and there is no such thing as “complete” testing, the amount of time spent on testing is always a balance between risk and other factors such as time and cost.

Someone has decided where that balance is on your project, so they are content with the risk that remains when you have used the time they allocated for testing.

You might not be happy with the remaining risk, but it’s probably not your responsibility to decide where that balance is. If it is your responsibility, then spend more time on testing if you think that’s the right thing to do. If you can’t for some reason, then it’s not really your responsibility after all.

I read that in the voice of a Dalek :joy:

A is for quality Assurance - although I dispute the notion that we as testers alone can assure quality, it’s a team effort.

One could make most of the words starting with ‘a’ about testing. And there’s a significant amount of them.

:astonished: You really can tell a testing story with all of these words! :heart:

A is for ANOTHER BUG!

A is for AAARGh! a common exclamation of frustrated testers

A is for Accelerate, Testers and Quality Engineers Accelerate their teams delivery.

Appreciate, the value of quality that testers/QAEs bring to any company.

A is for Ackoff. Russ Ackoff is one of the people who developed Systems Thinking, which is so helpful to improving quality. This is a ten minute video of him speaking about quality. After I had watched the video I felt that I had gained an insight: Beyond Quality Improvement Dr Russ Ackoff @simon_tomes It was great to talk to you at SIGiST. I hope that you like the video