Do you remember your first days as a new QA specialist on a project? There is much to be addressed all at once - testing itself, process maintenance, and knowledge gathering. Yet, numerous issues stand in the way: documentation does not exist, is outdated, or is overly detailed; tasks are poorly described or not described at all; requirements are changing, but this is not highlighted anywhere and is discussed only in direct messages (DMs) between a few people. Sounds familiar? Most likely, many QA professionals have faced such a situation at least once in their careers.

In addition, there are usually dozens or even hundreds of test cases to be maintained, or there are none, and it would be good to start writing them. How can teams handle all of this without going crazy? How can they make sure that the most critical areas are covered? The answer is to rethink how testing checklists are used. Documentation sometimes just needs a good pivot.

Natalia Romańska would like to share a solution for creating and maintaining this basic testing documentation. This solution was flexible enough for her to use when working with several different teams, with all the pros, cons, and lessons learned.