Rules Settings

Organization

Repository

Target Branch

Language

Edit scope

Docs

Allow the agent to edit implementation files

When off, the agent can only edit test files. Implementation files are protected: edits are rejected, and any coverage gap caused by dead code is accepted instead of the loop trying to reach 100%.

Comment Rules

Docs

Enable comments in generated test code

Include explanatory comments in test files created by GitAuto

Test File Location and Naming Rules

Docs

Test file location

Choose where test files should be placed relative to source files

Preferred test file naming convention

Choose how test files should be named

Test Constants Rules

Docs

Test constants management strategy

How to handle commonly used test constants

Unit Test Rules

Docs

Prefer function style over class style in tests

Prefer functional programming patterns in tests

Enable comprehensive test coverage including edge cases

Generate tests for edge cases, error conditions, and boundary values

Allow refactoring source code before writing tests

Allow GitAuto to refactor and improve source code structure before generating tests to keep the test code clean and readable

Component Test Rules

Docs

Prefer function components over class components in tests

Use functional components in test code when possible

Enforce component isolation in tests

Test components in isolation from their dependencies by mocking or stubbing external dependencies

Enable mocking external dependencies in component tests

Mock external APIs, services, and third-party libraries in component tests

Repository Rules

Define repository-specific guidelines that apply across all issues and users within the repository. Write any coding standards, preferences, or requirements that GitAuto should follow when generating tests for this repository.

0 / 5000 characters0 tokens

Rules Settings

Organization

Repository

Target Branch

Language

Edit scope

Docs

Allow the agent to edit implementation files

When off, the agent can only edit test files. Implementation files are protected: edits are rejected, and any coverage gap caused by dead code is accepted instead of the loop trying to reach 100%.