Trying to understand which tool is best
I'm trying to choose a test case management system for my project and would like to hear your opinion about following options:
- Atlassian Zephyr
- Gurok TestRail
- Microsoft Office Excel
- Google Spreadsheet
In case if you don't want to fall into deep discussion please fill in the voting form below: https://goo.gl/6l2dr4
You're going to select a test case management tool based on a poll of random internet users, rather than what your requirements are?
We all work in very different types of projects and with differing development/testing methodologies. Our project teams are different sizes, some may be co-located and others may be distributed, we will have different requirements for storing test cases (internally for functional testing, external for UAT, repeatable for regression, etc). You may or may not need to have links back to requirements or to defects/issues, the ability to export to a reporting tool or to link to a defect repository.
Why don't you start with your requirements, and then you may get a better idea of what may or may not work for you?
About 5 years ago I spent 3 months putting together a business case based on requirements and doing an in depths analysis with my team.
Originally Posted by kamenskiy
I can tell you off the bat, avoid Google Spreadsheet and Excel. They will give you more head aches later when you need to import into a proper TCM system. This is because there are too free form and you will end up creating disorganized piece of data, especially in big teams. You're better off using a cheaper intermediate TCM system that can export the data into a flat CSV file.
My experience has been..
- Zephr enterprise (not the Jira add-on edition) provides really great features for test organization and test planning. It was hard to make the business case for this one as the qualitative measures is hard to convert into $ figures. But from a usability perspective, I really like this one.
- TestLink - best out of the free tools I know. It's good for small projects, but because of their bad schema design, it gets exponentiallly slower as projects get bigger. The main culprit are nested test cases that causes cross joins. I would avoid TestLink unless you have access to a good DBA that can manage the database indexes.
- TestRail - I've implemented test rail at 3 different companies. I think it has a good mix of features for an entry level TCM. They recently added Jira integration which is nice, but I haven't been able to configure it yet. (office politics at my current place with our Jira is controlled by a different department) Test Rail is probably the easiest one to make a business case for. Priced at @ roughly $25/person its easy to say, if it saves you 5-15 min a person to compile a overall multi team test progress report and defect analysis, it saves a lower level test manager roughly $10k / year per person managed. The downside is they don't have a cheaper report or view only login. This means a test manager will usually have to create a report to send to his superiors for reference instead of having them look at it themselves.