AI policy at Testing Throughout

Where I use AI

  • Interactive explainers and tutorials — AI assists with building the interactive components (mind maps, sliders, quizzes). Every factual claim is checked against primary sources before publishing and Lee checks them too with occasional edits.
  • Code — some of this site's code is written with AI assistance, reviewed and tested by me.
  • Images — some illustrations and card images are AI-generated.

Where I occasionally use AI

  • Tests and deployment scripts — As a tester, part of this wesbite is to give me the opportunity to practice testing and keep up to date with the latest testing trends. This website is often "over-tested", and by that I mean the amount of testing performed on the site does not match the risk profile. At the end of the day, this is also a hobby and something I like to do in my free time.
  • Development and styling - This site started as a blog where I followed a pattern that uses github API to pull mdx files and render them dynamically. I started with all the code and styling done by myself with some help. Over time, I found I was spending too much time looking up front-end concepts and not delivering valuable resources. I'm not a professional web developer and have no intention of being one, so I think in this instance AI development has helped me increase workload.

Where I don't use AI

  • Blog posts — the opinions, experiences, and arguments in my writing are my own, written by me.
  • Testing claims — anything I say about how testing works comes from my own practice and reading, not from a model's summary.
  • Comments and replies — if I respond to you anywhere, that's me.

Why this page exists

Readers deserve to know which parts of what they're reading came from a human. This page follows the slash-page convention of declaring AI use at /ai. If my use of AI changes, this page changes with it.

Last updated: 10 July 2026