Indeed. You need: loggers, data generators, integrations with state probe points, data/result aggregators, etc, etc.

For massive numbers of tests, now it's time to look into parallelism. Really hope you're not sharing your test data between test cases! Or holding open a single db session to your write instance!

How about multimedia artifacts management?

Point being, test automators do a shit ton of work nobody ever wants to dig into.

Tests are not there to only be written. They must be read.