Currently, our QA team writes test cases for every feature and bug fix. These take the form of spreadsheets - each row is a test case with name, steps, prerequisites, outcome of the test (pass, fail). The spreadsheets are attached to the feature ticket in Jira (our issue tracking system). QA team members review each other's test cases.
Problems with this:
- This is purely change oriented. To figure out how a feature is supposed to work right now, you have to go through the tickets related to the feature to piece together the complete picture. Same to assemble test cases to regression test the feature.
- Getting test cases reviewed involves passing spreadsheets to members of the QA team, keeping track of feedback, etc.
This has already been solved in the dev team using Git:
- Code changes are expressed in commits, which live in branches.
- There is one unified "live" version of the code base, and one "next release" version.
- To get feedback from other devs, a developer creates a Pull Request in Git. This supports discussion, etc. No passing files around, sending emails, etc.
- Git keeps track of all changes, etc.
I suggested to the QA team to write test cases in text files and storing them in Git. They are intrigued but also somewhat apprehensive about this.
- Feedback from other QA teams re. this idea.
- Your experience re. what happened when you introduced a similar scheme in your QA team.
- Any QA oriented tools or services that allow you to store test cases per feature, to reviews, etc.