Tusk is optimized for Ruby unit test generation in a way that the base models in your AI-powered IDE are not. Our tool also sits in your CI/CD pipeline, so you get automatic unit test coverage without having to tediously prompt in a chat-based interface.
Yes. You can review the unit tests generated for your PR/MR in our web app and select which test cases should be committed. Tusk does not auto-commit the tests it generates.
We are SOC 2 Type II certified. Tusk and our LLM providers do NOT use your source code to train models. Tusk uses multi-tenant architecture, so your source code will never be accessible to other customers.
Tusk runs when you raise a PR/MR and on subsequent commits to the PR/MR's branch. It generates unit tests according to the symbols modified in the PR/MR. For backfills, you can leave a comment in the symbol definition. More in our docs.
Yes. You can use Tusk as a form of code review on your PRs or MRs. However, we are focused on helping you scale your testing infra, as opposed to helping you catch issues with code style.
Tusk integrates with GitHub and GitLab for version control. Our tool also integrates with Linear and Jira in order to extract business context from project management tickets that are linked to the PR/MR.