Since CAST 2015 I’ve wanted to implement an interesting idea that could potentially give my testing greater visibility and greater scrutiny: [highlight]putting exploratory testing charters into our project tracking tool.[/highlight]
At work we use GitHub to host our code which means we use GitHub Issues as our bug tracker. Then we use ZenHub on top of GitHub Issues as project management / tracking tool. As the sole (omega) tester on the development I use GitHub issues for a number of activities:
- Filing and reviewing issues (bugs and enhancements)
- Occasionally reviewing pushed code changes referenced in the issues I’m tagged on
- Occasionally reviewing pull requests
- Committing the rare change to our production code (I’ve done this once so far)
- Committing code changes to our test automation repo
Do charters belong?