-
Notifications
You must be signed in to change notification settings - Fork 128
Future of testing #382
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Future of testing #382
Conversation
csalt-scottlogic
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I like it; can you update the date and shorten the summary, and then we can get it published
| - AI | ||
| - Future | ||
| - Testing | ||
| summary: "The role of the Software Test Engineer is undergoing its most radical transformation since the advent of Agile. AI presents a fundamental bifurcation in the future of quality: Testing AI systems and Using AI to Test software. This post explores the evolution of testing from manual gatekeepers to modern, multi-skilled strategists. We detail the deep analytical skills required—from Prompt Engineering and AI-Augmented Toolsmithing to Ethical and Bias Testing—as the focus shifts from writing scripts to interpreting data and orchestrating advanced AI co-pilots. Learn how embracing this change elevates the Test Engineer to a crucial strategic role, driving superior quality, faster releases, and ethical AI deployment." |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The summary feels a bit long. I'd take the last two sentences off
| The traditional role of the software tester used to be as a gatekeeper, script writer, and manual executioner; a role often filled by accident and amalgamated into large teams of bug hunters, directed to perform repetitive, low-skill tasks. They were the sentries guarding a fixed fortress, checking every latch and bolt on the drawbridge. However, there were always mavericks—testers who went off the beaten path. These individuals eschewed standard processes, hunting on their own or in smaller packs. They were explorers and cartographers, taking an interest in the underlying mechanisms and domain, and could identify the path to follow without the rigid need for pre-drawn maps. | ||
|
|
||
| ## The Evolution of the Quality Guardian | ||
| Today, the modern tester is a Quality Guardian and a strategic architect. They are multi-skilled, required to code, assess risk, analyse data, and communicate across many different boundaries. They must think critically, see the big picture, and possess domain knowledge. They have shed the armour of the sentry and now serve as the chief adviser on risk, performance, security, and accessibility. All the while, they are beholden to delivery expectations and time pressures, relentlessly seeking the very structural weaknesses that threaten the value of the software being produced at an ever-increasing velocity. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a thought: does "strategy architect" make more sense than "strategic architect"? The tester is an architect of the strategy, not an architect who behaves strategically?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Kind of both really. They architect tests, strategically. And is an architect of the testing strategy. Both make sense here.
Please add a direct link to your post here:
[https://demcnamee.github.io/blog/2025/11/19/ai-testing-bifurcation.html]
Have you (please tick each box to show completion):
npm installfollowed bynpx mdspell "**/{FILE_NAME}.md" --en-gb -a -n -x -tif that's your thing)Posts are reviewed / approved by your Regional Tech Lead.