Skip to content

Instantly share code, notes, and snippets.

@freemo
Last active February 27, 2026 17:10
Show Gist options
  • Select an option

  • Save freemo/f88125c2c74eebc796cc27874169ec63 to your computer and use it in GitHub Desktop.

Select an option

Save freemo/f88125c2c74eebc796cc27874169ec63 to your computer and use it in GitHub Desktop.
Review the current unit test coverage report at `build/coverage.xml` and use it to write new Behave based unit tests to improve code coverage. Specifically, write Behave style unit tests that are descriptively named and specifically improve coverage on file `$$FILE_PATH$$` by writing tests that will target the uncovered lines in the report.
Review the current unit test coverage report at `build/coverage.xml` and use it to write new Behave based unit tests to improve code coverage. Specifically, write Behave style unit tests that are descriptively named and specifically improve coverage on the current file changes waiting to be committed to git by writing tests that will target the uncovered lines in the report. You should start by viewing the current code changes that need to be covered by running command `git diff HEAD`.
Review the current unit test coverage report at `build/coverage.xml` and use it to write new Behave based unit tests to improve code coverage. Specifically, launch agents in parallel to write Behave style unit tests that are descriptively named and specifically improve coverage on each of the following files: `$$FILE$$`, `$$FILE$$`, `$$FILE$$`, and `$$FILE$$` . Be sure you launch exactly one agent in parallel for each file. Once all parallel agents complete run `nox -e unit_tests` to confirm all tests are working, if any errors are produced fix those, repeat this until the unit tests all pass.
Also make sure the new code written for this coverage is done in a new branch, create an issue and pull request on Forgejo to cover this task, follow the guidlines in @CONTRIBUTING.md to ensure everything is in compliance with the project's
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment