Making each an individual test would triple the test time, pollute the test codebase and not bring any advantage.
Would it really? None of what you said here is true.
Ideally, if just one assert fails, it will produce an error message/logs with enough info to tell what went wrong. Having tests produce great error messages is way more valuable than arbitrary rules about assertion density.
I bet the tests aren't pixel-by-pixel frame-by-frame reproducible (they are talking about a one week staging period for tests to prove themselves, so surely there's some non-deterministic wiggle room in remote controlling the full graphical client), so you really want to cover all assertions together for each run.
It's just hard sometimes to set and follow standards when you're pushing to demonstrate value. Not impossible, but hard.