AMA about System Testing

Where is systems testing heading in the age of AI?

How do you define 'system' in system testing? Also, you should write a glossary entry for it.

If you could create a new system testing model to debunk the automation pyramid, what would it look like?

Hello all! I'm sorry for the delay, I actually thought I'd get an email for responses. Simon pinged me to let me know I was missing all of your questions.

Rosie, You could certainly argue (and I would) that Systems Testing is going to stay at least as important, if not more so in the age of AI. One example I can think of is if you're brought in to work on an existing system that was heavily written using AI. The code base may not have sufficient coverage at the unit or integration levels, which can cause some real concern when trying to make changes or refactor.

(Cont.) If you build up system level tests, you can update the code underneath with more confidence (and build up your other levels of testing while you're at it!). We've actually seen this situation at our company already, and I can imagine a lot of Vibe Coded applications exacerbating this. On the other hand, using agentic tools, we've started finding ways to build some of our system level testing faster, and with guardrails to make us confident in what is actually changing.

Ady, I define system testing as any testing that exercises the application under test as a user in order to verify that it works properly. A system is any piece of software a user interacts with. (note that this doesn't always mean the user is a human. You can have other pieces of software that interact with your software. Those are users too!) Good idea to add it, before I do, any thoughts on my definition?

Simon, I've experimented with this a few times! Currently, I am in favor of the Round Earth Test Strategy found here: https://www.satisfice.com/blog/archives/4947 I've been toying with the idea of modeling it after a hot air balloon, but I might be trying to be too cute with it.