Not finding adequate answer to my question on the internet I thought I would share it here.
If you have 3 categories to test: UI, Audio and Network.
A) Do you do 3 tests per category but then it duplicates itself like “Go to X and verify UI”, “Go to X and verify Audio”, Go to X and verify “Network”?
B) Do you do 1 test per functionality and do “Go to X and verify UI, Audio and Network”
A is clearly readable and if audio fails you know that functionality X failed in audio you know exactly what happened. This is at a cost of checking same functionality 3 times but from 3 different perspectives.
B) Removes redundancy of tests but if it fails you know that X functionality failed but you don’t know what exactly failed.
The other part is I have testers per category, for audio, art, ui, network etc. so we are preparing Audio test suites, UI test suites etc. This makes it easier to maintain and we know which category is in what state instead of what functionality which is more or less natural cause we have teams dedicated to category not functionality.
Then again is it bad to have redundancy in such cases? Any thoughts how to approach it? Do you have any good materials on the subject?