Hey everyone! My web development team is expanding, and our current testing setup is becoming a bit chaotic. We handle a mix of manual and automated testing with tools like Cypress, Playwright, and Jest, and we also use CI/CD through GitHub Actions or Jenkins. The challenge is that our test cases and results are scattered, failures aren't consistently linked to issues, and our dashboards don't provide a clear status. I've looked into tools like TestRail, Qase, Zephyr, and Tuskr, with Tuskr seeming appealing because of its built-in integrations and automation features like webhooks to connect test failures to bug trackers. I'm eager to hear from anyone who has real-world experience with these tools. What are you currently using, what features do you find most helpful, and what trade-offs have you considered regarding maintenance versus functionality and cost?
1 Answer
I've been using Tuskr for a few months to manage our web app testing. It replaced a lot of manual tracking we had with Excel sheets, and I love how smooth the setup was. The interface is user-friendly, so our onboarding went really well. We can upload test cases via CSV, link it with our CI/CD pipelines, and connect failures back to issues easily. It has genuinely saved us time and reduced noise in our workflow.
That’s awesome to hear! The CSV import and CI/CD hooks sound like exactly what we need right now. Just out of curiosity, how has it been holding up as your test suite grows? Are the dashboards and reports still manageable, or do they get clunky as the number of tests increases?