Nordic Testing Days 2026

Testers often need custom tools - data generators, mock services, internal dashboards, or CI helpers - but building them traditionally requires significant development effort and prioritization. With modern AI-assisted coding, we can now prototype and build these tools themselves, minimizing both engineering and maintenance efforts. In this session, I’ll show real examples of using vibe-coding to create internal testing workflows, interfaces, and CI/CD helpers. I’ll focus on where AI significantly accelerates development, where it introduces risks, and how to apply guardrails to keep these tools maintainable, secure and trustworthy.Rather than promoting “AI replaces engineers,” this talk presents AI as a practical productivity amplifier for experienced testers who understand their systems and constraints.


Key takeaways:

1. How to design and build tester-owned tools using vibe-coding without creating technical debtAttendees will learn how to approach AI-assisted development of internal testing tools (data generators, mock services, dashboards, CI helpers) with clear ownership boundaries, architectural decisions, and sustainability in mind.
2. A realistic mental model for AI-assisted coding in testing workflowsParticipants will gain a clear understanding of where vibe-coding provides real leverage for experienced testers, where it breaks down, and how to critically evaluate AI-generated code instead of blindly trusting it.
3. Practical guardrails for security, maintainability, and long-term useAttendees will leave with concrete strategies for applying constraints - such as validation, code structure, reviews, and documentation - to ensure AI-built tools remain trustworthy, auditable, and safe to evolve over time.

SummarySecurity testing sounds like it might be best left to the “experts”, whoever they are, but I will share how we can include it in our day-to-day testing. From exploratory testing to API and automated testing, there are things that we can and should be doing.Through this workshop we will learn about the scope of security testing, find out about the automated tools available and then spend some time practicing basic security testing techniques like SQL Injection, Insecure Direct Object Reference and using browser developer tools.Setup- Attendees will need to bring a laptop or pair up. Any browser is fine but Chrome recommended. - Screen & HDMI/equivalent for presenting slide & demos.ActivitiesFor a 2 hour workshop:- IDOR / URL manipulation- Bypassing UI using developer tools- Cross site scripting (XSS)- SQL injectionIf a 4 hour workshop is preferred, I can add in additional activities including analysing session data and a Capture the Flag exercise.

Key takeaways:

1. Recognise that security testing is something that you can & should be doing
2. Identify the "low hanging fruit" security bugs in software
3. Execute basic penetration tests against an online system