Aj Wilson
Aj Wilson
Quality Engineering Manager II / Technical Development Lead / Chief Quality Officer/ Digital Test Manager
She/Her
Intellectual (non practicing)| Neurospicy | UN Women Delegate | Above all Curious; Challenging - Quality and Tech Leadership for 20+ years.
🎂 MoTaBirthday | March 23, 2018
Open To
Write
Teach
Speak
You cannot claim a system is or uses "Responsible AI" just because there is a human button-pusher. If the system is designed to move faster than that human can think, how do you prevent your busine...
30 Apr
Cloudflare went down again today and half the internet with it. Nothing like a global outage to remind us that we're all just one code or config change away from cup of tea time chaos.
19 Nov
A self-spreading malware called GlassWorm has infected OpenVSX and one VSCode extension (cline-ai-main.cline-ai-agent v3.1.3), enabling it to propagate across systems and steal data. This supply ch...
28 Oct
Is the future of test case management at risk? Let's go exploring.
28 May
63% of you were not aware of the existence of the Staff Quality Engineer role
24 Apr
This debate explored the role of quality coaching, how it differs from quality engineering and where it is most effective
1 Apr
Obfuscation
Obfuscation is the process of replacing sensitive information with data that looks like real production information, making it useless to malicious actors. People often confuse Anonymisation & Obfuscation, they are both data protection methods, but they differ in reversibility, purpose, and legal standards. Anonymisation permanently removes all personal identifiers from a dataset so that individuals can no longer be identified. Obfuscation alters the data's format or replaces it with fictional values (using methods like masking, encryption, or shuffling) to hide original information, though some forms remain reversible or readable by the systemKey Differences checklist ㊙️
Reversibility: Anonymisation is permanent and irreversible; obfuscation can often be reversed by authorised parties using a key or code.
Primary Goal: Anonymisation aims to completely sever the link to an individual for strict privacy compliance; obfuscation aims to deter casual observation or protect data during development and testing.
Regulatory Status: True anonymised data is exempt from strict laws like the GDPR because re-identification is impossible; obfuscated data is often still regulated as sensitive or personal data.
Use Cases: Anonymisation fits open data sharing and public research; obfuscation fits software/quality engineering, internal analytics, and staging environments.
Anonymisation
Anonymisation is the process of irreversibly removing or encrypting personal identifiers, such as names, addresses, and ID numbers from a dataset. The goal is to protect individual privacy while allowing the remaining data to be safely used for software testing.How it works: It involves techniques like generalisation (broadening details), masking (redacting), or adding random "noise" to the data. True anonymisation is irreversible. Once processed, it is nearly impossible to trace the data back to an individual.
Why it matters: Anonymised data falls outside the scope of strict data privacy laws (such as the EU GDPR) because it no longer relates to an identifiable person.
Velocity
Velocity is a metric used to track the rate of progress in software development. For testers, the term carries two distinct meanings that impact how quality and timelines are managed.1. The Agile Metric (Operational)In standard Agile practices, velocity is the total number of story points a team completes during a sprint.For Testers: It serves as a capacity planning tool. A spike in velocity without a corresponding increase in team size often signals "testing debt," where speed is prioritised over thorough validation or regression testing.2. The AI/Market Narrative (Strategic)In the current "AI-first" landscape, velocity refers to the overall speed of deployment and organisational pivot.For Testers: This is often viewed critically as "speed over direction." High organisational velocity can lead to "accelerated chaos" if the testing infrastructure - automated suites, environments, and safety rails - isn't scaled to match the increased deployment frequency.
JNTX System
A JNTX system is a specialised software architecture used in AI-native and agentic platforms. Instead of relying purely on traditional, hard-coded logic, it deploys features and functionality using a combination of autonomous agents and prompts. For software testers, this means shifting from validating deterministic code to validating probabilistic interactions driven by Large Language Models (LLMs).As JNTX platforms scale, QE's or QA teams frequently encounter a major architectural risk known as "prompt spaghetti." This occurs when integration logic becomes overly complex, and developers attempt to handle system parsing and routing directly within natural language prompts.
For a tester, prompt spaghetti results in:
Highly brittle systems that are nearly impossible to reliably automate.
Non-deterministic outputs that cause widespread flaky tests.
A massive increase in edge cases, hallucinations, and unhandled exceptions.
Service Mesh Testing
A service mesh is a dedicated infrastructure layer that controls how microservices share data with one another. It uses "sidecar" proxies to automatically handle networking, security, and monitoring so software engineers don't have to build those features into the application code. Service Mesh Testing is the practice of validating how microservices interact by using the network layer that connects them. Instead of testing a single service in isolation, you use the service mesh to run "what if" scenarios and safety checks on the live connections between services.
Think of it as a flight simulator for your software network that enables several advanced testing strategies:
Canary Testing: Gradually routing a small percentage of users (e.g., 1%) to a new update. If the metrics look good, you "dial up" the traffic; if not, you roll back instantly with minimal impact.
Traffic Shadowing (Mirroring): The mesh creates a "ghost copy" of real user traffic and sends it to a test version. This allows you to see how new code handles real-world stress and data without the users ever knowing or being affected.
Fault Injection (Chaos Engineering): Programmatically forcing the network to act as if it is slow or as if a service has crashed. This confirms the system is resilient—staying upright even when individual parts fail.
Observability "X-ray": Provides a real-time map of every conversation between services. If a request fails, the mesh shows you exactly where the chain broke, eliminating the guesswork in debugging.
Why it matters: Traditional testing often happens in a "lab" (staging environment) that never quite replicates the real world. Service mesh testing allows teams to test against real-world conditions with granular control, significantly reducing the risk of deployment failures.
Comments
(8)
How I built a PR dashboard that flags risky pull requests
Progress over Perfection for the win! This is a great example of using data to drive better engineering conversations rather than just reporting status. The RAG indicator is a useful prompt for discussion, and I like that it focuses attention on risk, test coverage, and review effort without pretending to be a perfect quality metric. Thank you for sharing.
LGBTQIA+ Pride Month — Visibility matters: You are not alone
thank you for repeatedly empowering and educating
Possibly late to the party, but something I couldn't pass up
tried the same prompt - despite using it for a long time it still assumed I was a man lol because of my "masculine name".
What's your AI name?
AiJ
(pronounced Age)
* which is also the Artificial Intelligence Journal
*Math - (\(a_{ij}\))
*Architectural Institute of Japan
*Architectural Ironmongery Journal
Getting paid what you are worth as a software tester
Theres no mention of DEI, Employee trust or culture. When researching companies transparency is key. Salary secrecy can perpetuate systemic inequalities, especially affecting women, minorities, and underrepresented groups who statistically negotiate less or are offered lower starting salaries. And secrecy affects morale and trust. Employers need to understand the data better - transparent pay practices often correlate with higher engagement, while secrecy can breed suspicion and disengagement.
Self-spreading GlassWorm malware hits OpenVSX, VS Code registries
(www.bleepingcomputer.com)
28 Oct 25
15 May 25
Observatory Enabler
This badge is awarded to those tagged in their first Observatory link.
Badge Award
2 days ago
Moment-um Builder
This badge is awarded to those that have been tagged in their first Moment.
Badge Award
2 days ago
Learner completed your lesson
2.3.0 of MoT Software Quality Engineering Certificate
Community Star
2 days ago
