| || |
Best Test Management Tool
I have explored few test managment tools. e.g Testlink, testlodge, qmetry and test rail. I like testlodge best due to quick configuration , ease of use and its compatibility with you track. Please guide is my decision best. Would love to get more suggestions in choosing a best tool.
What are your requirements for reporting, number of users, platforms, capabilities, integration with existing tools, etc....? What is optimal for you will be driven by your defined requirements. I could make lots of assumptions on what you need, but they would be just that, "assumptions," with zero basis for grounding with your organization. Or I could just say, "use tool A, it it is best. It is pricey, but it is worth every stinkin' penny (assuming you are willing to invest in the right people to install it and you are willing to train your users in how to use it effectively. It usually covers about 95% of any given organization's needs and you can customize it for the last 5%....."
We are using Windows system. There are more than 10 employees involved in testing. We are using youtrack to report any issues and reporting is the high priority task. If tool gives the ability to efficiently create test plans and manage them effectively then price is not the issue.
Out of those, I've worked alot with TestLink and Test Rail, and tried out TestLodge.
I personally like Test Rail over Test Lodge because of they allow you to organize your test into a hierarchy. To me it's overwhelming to have a long list of test cases, and I like to have logical groupings behind them. Both are pretty simple to use. I also like how they both have a nice REST api to do the basics of what I need to get automation reporting their results back to the TCM.
TestLink being open source is nice. But I really hate the performance on it and their API is very limited compared to TestRail and TestLodge, which made it hard to integrate with the CI build pipelines I've designed. On the performance, TestLink has a huge fundamental flaw in that is has a flat database to represent a tree structure. What ends up happening is there are multiple places where it does database Joins on itself, causing exponential slow down with each nested tests. When I was forced to work with TestLink at a shop that was already using testlink, we had to do heavy customizations to add custom indexes and database caching to avoid that issue where it would break if you had too many nested test cases. On the integration, they didn't appear to have a clear REST api at the time I was evaluating them, it has hard to make my automated tests do more complicated things like query the latest active test plan and report back their results. I was writing a lot of complicated SQL queries and joins in order to report the automation results. I believe they have some sort of API now, but haven't worked with it recently so I don't know how robust or easy to use API is now.
I have not worked with qmetry
Last edited by dlai; 01-03-2015 at 07:03 AM.
Manual? Automated? Performance? Security? Will you be tracking requirements and need integration with a requirements management system? Similarly, do you need to integrate with an existing defect tracking system? Do you have existing automated or performance tools that you need to integrate with? Do you need out of the box to cover everything or is custom reporting an option? Requirements coverage reporting? Defect to requirements? Thick client or browser support? Which browsers and versions?......
You are a quality assurance professional: Nail down your requirements. Get to something which is Specific, Measurable, Attainable, Results-Oriented and Time-based (SMART) - Something which can be evaluated to "Yes" or "No" on your tools eval. Rank them in order of most to least important. Otherwise you are going to be subject to the winds of the day which blow or vendors who will turn on fans to blow you one direction or another. Take a step back and write down specifically what each of your role members need to do their job effectively and convert those to requirements. Then use those requirements to evaluate your options. Make your work subjective and use the skills you have brought to the party in terms of requirements collection, analysis and examination.
I work on an open source test management tool named Squash TM. Squash TM is a web-based application for managing requirements, tests cases and runs. Users of Squash like the intuitive approach and the easy of use.
Squash, Eggplant, cucumber, gerskin,
Sounds like a salad about to be made.
Bob's homegrown spreadsheet model!
Pen and Paper!
Until you know what you need all tools are equal and lowest price wins. Once you understand what you need then you can place a value on each requirement which allows for a full valuation of the market offerings.
Last edited by jpulley3; 01-11-2015 at 07:17 AM.
You can try PractiTest
To add one more to the Tools (Virtual) Salad, I wanted to suggest PractiTest (the company I work for).
We have a tool that gives you the ability to manage the testing process from reqs to tests and issues, it also has a pretty good dashboard and reporting module that will help you with your reporting needs. The system is good for all Operating Systems and browsers, with the available API you should be able to integrate it to yourtrack if you want, and it is pretty easy to set up and work.
You can check out a demo from here - PractiTest.
Good luck with your search!
We have used, TestLink, Qmetry and now we are experiencing Occygen.They built new release Occygen v7 for 2015 and looks too professional.
You can take a look on www.occygen.com