Hey everyone! My web development team is expanding, and our current testing process is starting to feel chaotic. We're juggling both manual test steps and automated tests—using tools like Cypress, Playwright, and Jest—and we also have CI/CD set up through GitHub Actions or Jenkins. My main issues are that our test cases and results are all over the place, and failures aren't consistently linked back to bugs. Plus, our dashboards don't paint a clear picture of our testing status.
I've been looking into various tools, including TestRail, Qase, Zephyr, and Tuskr. Tuskr caught my eye because it offers built-in integrations and features like webhooks and Zapier to help automate the linking of test failures to bug trackers. However, I'm not entirely convinced yet. I'm really interested in hearing from those who've used these tools in real projects. What tools are you currently using? What features are must-haves for you? What compromises have you had to make in terms of maintenance, functionality, and cost?
1 Answer
I've been using Tuskr for a few months now, and it's really streamlined our web app testing. It replaced a lot of manual tracking we had in Excel, and honestly, the setup was a breeze. The interface is clean, which made onboarding pretty quick. We can easily import a bunch of test cases via CSV and integrate with our CI/CD pipelines, linking failures back to issues without too much hassle. For us, it's saved a lot of time and cut down on confusion.
That's great to hear! The CSV import and CI/CD integrations are exactly what we're missing right now. But how does it hold up as your test suite grows? Are the dashboards still user-friendly, or do you feel the need to export data as things get bigger?