Ideal workflows for using Tusk as a developer
Tusk - Generate Tests
GitHub/GitLab label to the PR/MR. This label is automatically created when you connect Tusk to your GitHub organization or GitLab group/project.
Create a draft PR
Tusk generates tests
Review Tusk's tests
Commit Tusk's tests
Fix failing tests
[Tusk] FAILING TEST
comment in the test file for ease of reference.Engineer re-runs the test file to make sure the failing test now passes, removes the [Tusk] FAILING TEST
comment, and pushes the fix.Mark PR as ready
Merge the PR
Create a PR
Merge the PR with the hotfix
Tusk generates tests
Create separate Tusk PR
Fix failing tests
[Tusk] FAILING TEST
comment in the test file for ease of reference.Engineer re-runs the test file to make sure the failing test now passes, removes the [Tusk] FAILING TEST
comment, and pushes the fix.Approve and merge the Tusk PR
Edit preferences
Disable automatic test runs
Create a PR
Trigger test generation
Tusk - Generate Tests
GitHub/GitLab label to the PR/MR to generate unit tests for your changes.Tusk generates tests
Commit Tusk's tests
Fix failing tests
[Tusk] FAILING TEST
comment in the test file for ease of reference.Engineer re-runs the test file to make sure the failing test now passes, removes the [Tusk] FAILING TEST
comment, and pushes the fix.Merge the PR
Find a past PR
Trigger test generation
Tusk - Generate Tests
GitHub/GitLab label to the PR/MR to generate unit tests for the code changes.Tusk generates tests
Create separate Tusk PR
Fix failing tests
[Tusk] FAILING TEST
comment in the test file for ease of reference.Engineer re-runs the test file to make sure the failing test now passes, removes the [Tusk] FAILING TEST
comment, and pushes the fix.Approve and merge the Tusk PR
CoverBot runs on schedule
CoverBot creates a PR
Review CoverBot's tests
Modify tests (optional)
Handle detected bugs (optional)
Merge the CoverBot PR