As I previously hinted in “Building a test case management solution”, I’m personally of the opinion that the holy grail in test case management is in finding the way to manage tests via an issue tracker database.
In the time since that post I didn’t find much information about this, and didn’t see tools taking this approach.
Therefore, it was great to stumble upon Agile06 – François Beauregard – GreenPepper Software – a podcast discussion where I learned about greenpepper, a test automation and management system developed by Pyxis Technologies which closely integrates with JIRA to create an issue tracker solution for managing test cases, and adopts a Fitnesse-like approach (on drugs) to table-driven testing, over the Confluence wiki. I liked the choice of tools to integrate with as well as the pragmatic simple ideas.
Last week Frank and Christian demonstrated the system to me and a colleague. I was impressed, and would recommend anyone with interest in the test management or issue tracking domain to track those guys. I know I will.
One issue I’ve been thinking over regarding both Fitnesse and GreenPepper is how to take those tools that are focused on one-shot automated testing, and adapt them to track manual testing documentation, results, etc. Finding a good way to solve this problem might assist with adoption of those tools/frameworks in environments which are not the classic agile web development environment I suspect are the majority of adopters at this point.
I'm Yuval Yeret. I'm leading the Kanban practice at AgileSparks. This blog focuses on my experiences using Lean and Agile approaches to help organizations and people become more effective.
Top Posts & Pages
- My favorite Excel-based Agile Backlog Templates
- Making Agile Teams work in real life - The quest for Stable Feature Teams?
- So what IS Scrumban?
- Agile antipattern: Code freezes during each iteration
- Kanban Method - Finding the Minimally Viable Change
- Bootstrapping Agile (by yourself) using Kanban - My Agile Israel 2013 talk
- Do Craig Larman's Laws of Organizational Behavior really mean we always need to start with a structural change? What do they say about starting with Kanban?
- Don Reinertsen's Cost of Delay Intuition Exercise - a facilitator's guide
Tag cloudkanban iterations conference greenpepper QA relationships RND issue_tracking LimitedWIP metrics SPC Workshop Organization bugs agile testing MMF engineering_practices Commitment agile_testing LSSC11 lean agile Training Cycle_Time scrum flow resources קנבן Lean Startup Continuous Improvement Transition sprint velocity Israel SLA project_management LSSC12 Teams LKCE11 hr Slack classes of service reading_materials test_case_management Agilesparks
This work by Yuval Yeret is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 3.0 Unported License.