Final Build Checklist Testing, Suggestions?

Hey guys,

We've got a couple of titles under our belt, and no matter how strict our testing is, something always catches us off guard. How do you guys combat your ongoing bug battles with increasingly complex projects? I would love to hear how other people deal with these things

For iOS, I have a few rules.

1. One week prior to Release Candidate, Asset Server is banned from use (in case other coders break things), and it becomes a single machine pipeline.
2. After Unity produces an RC Build to Xcode, Unity is closed, and will not build again unless the RC fails with a critical bug.
3. Each RC must undergo a large list of tests, each feature has to be tested, and must survive 6 hours of testing from at least two people (optimally 4).
4. Each build also has a checklist (which I've included for interests sake).
5. If the RC passes, the Xcode project that was used to build, is used to submit. Unity at this point should have been untouched for the entire duration of testing.
6. Each column has to be signed [by hand] by whoever has declared it passed.

Example RC-Build Checklist​

 

Hey,
do you have an update and editable version of that Checklist?

thanks!