Dev's make suggestions but writing tests falls mostly on the QA's shoulders at Paradox, especially on the internal team. We have standard test cases but those are the minimum that we employ, a lot is on the creativity of the QA and sourcing ideas from the team.
This is the better way to do it in my opinion - a dev will think about how something is supposed to work in the box they've designed, experienced QA tend to think of what it touches that the dev may have forgotten about.
There is a lot of conversations about this which happens regularly in the office, it gets people talking about the features and it helps educate other devs about how things interact. It also leads to fun situations: I've once seen the face of a designer go pale as he overheard QA talking about X feature and how it works, as they had realized they had just merged a "fix" that broke a significant portion of the game
. They then remedied this error pretty quickly.- 23
- 9
- 4
- 2
- 1
