CodeBeaver understands your codebase, runs your tests, and writes them if needed.
Your development team opens a Pull Request or commits new code to your repository (Read the documentation about triggers)
CodeBeaver automatically runs your existing test suite against the changes. In most cases, there's no setup required – CodeBeaver analyzes your codebase and intelligently determines how to run your tests.
If any test fails, CodeBeaver analyzes the failure and determines if it's due to a bug or to an old test.
After finding a bug in the code being tested, CodeBeaver writes a detailed report to help you fix the bug.
When necessary, CodeBeaver generates new tests or updates existing ones to ensure comprehensive test coverage.
CodeBeaver validates all newly generated tests by running them against your codebase, discarding any that fail to perform as expected.
Just like a human developer, CodeBeaver executes any configured pre-commit hooks and additional checks in your workflow.
CodeBeaver creates a new Pull Request in GitHub, GitLab or Bitbucket, using your original code changes as the base. The PR appears in your workflow just as if it came from another member of your development team.
CodeBeaver integrates with GitHub, GitLab, and Bitbucket, so you can use it in your existing workflow. We also support GitHub self-hosted.
CodeBeaver can automatically configure itself for common frameworks, such as pytest, unittest, jest, and so on.
CodeBeaver can kick in automatically every time you open a Pull Request. But you can also activate it for a specific set of files, for your whole codebase, for a particular commit.
Got pre-commit hooks in your repository? Great. CodeBeaver respects and executes any pre-commit hooks you have configured, ensuring a consistent workflow. No need to set anything up.
Get started and see how CodeBeaver can help you write Get Unit Tests with Every Pull Request.
Get started