Make the testing checklist great again! Handling test documentation

Balancing testing, process maintenance, and knowledge gathering is tough, especially when joining a new project. Yet, numerous issues stand in the way – documentation doesn’t exist, is outdated or over-detailed; tasks are poorly described or not described at all; requirements are changing – but it’s highlighted nowhere, being discussed only in DMs between few people… Sounds familiar? We most likely faced such a situation at least once in our careers. So, how to stay sane and handle all of this? The answer is – to revamp testing checklists!

I’d like to share a solution for creating and maintaining this basic testing documentation. A solution, that turned out to be flexible enough and has been used when I had been working with several different teams – with all the pros, cons, and lessons learned.