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
- Book Report - Developing Products in Half the Time: New Rules, New Tools by Reinertsen and Smith
- So what IS Scrumban?
- Don Reinertsen's Cost of Delay Intuition Exercise - a facilitator's guide
- Kanban Method - Finding the Minimally Viable Change
- Addressing some myths and misconceptions people have when considering Kanban
- How to replace the timebox-based motivation when using Kanban/ScrumBan
- Severity and Priority - The Debate
- Kanban FAQ: Should I FINISH what I'm working on or help the team READY new work items?
- May the WIP Games begin...
Tag cloudOrganization greenpepper Agilesparks issue_tracking Israel SLA Transition QA Cycle_Time scrum Slack lean RND metrics קנבן conference Workshop Commitment reading_materials sprint classes of service flow agile Teams MMF Training LimitedWIP relationships engineering_practices bugs Continuous Improvement project_management velocity agile_testing agile testing resources LSSC11 iterations LKCE11 LSSC12 SPC hr test_case_management kanban Lean Startup
This work by Yuval Yeret is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 3.0 Unported License.