Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -9,6 +9,15 @@ This changelog is automatically generated by AI when releases are published.

## [Unreleased]

## [3.13.0] - 2026-11-17

### Added

- **`autter tests`: run the tests Autter wrote for a pull request on your machine.** When a review's generated tests catch a bug, the failing test is never committed to the PR (it would turn CI red), so until now there was no way to pull it into your own environment to debug it. On the PR's branch, `autter tests run` writes the failing tests Autter kept into your checkout and runs each one with its framework's command (vitest, jest, mocha, `node --test`, pytest, `go test`, `cargo test`, rspec, phpunit) from its project directory, with `CI=true`. Fix the bug and run it again to see it pass. `autter tests list` shows what Autter wrote: which tests failed, where and why, which passed, and what could not run in its sandbox. `autter tests pull` only writes the files, and `autter tests clean` removes exactly what `pull` or `run` wrote (a file you edited stays unless `--force`). The PR is the one open from your current branch, or `--pr <n>`; `--all` includes the passing tests and `--only <path>` picks one. If your checkout is not at the commit the tests were checked on, a note says so.
- The tests are model-written from the PR's code and run here with your environment, not in Autter's sandbox, so `run` asks before it runs anything (`--yes` skips the question; without a terminal it refuses; `--dry-run` prints what would run). The CLI builds each command from the test's framework and path and never executes the command string stored on the server. `pull` never overwrites a file it did not write.
- A test that ran against Autter's temporary database runs only with `--database-url <postgres-url>`, pointing at a scratch database it may write to, and gets the same variable names Autter set. It never inherits your `DATABASE_URL`.
- `--json` prints one JSON document for scripts and coding agents (the test runner's own output goes to stderr). It uses your `autter login`; in local mode, or for a repository excluded from sharing, nothing is sent. It needs the Autter API with the generated-tests route; until that is deployed the command says so.

## [3.12.0] - 2026-11-15

### Fixed
Expand Down
2 changes: 1 addition & 1 deletion Cargo.lock

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

2 changes: 1 addition & 1 deletion Cargo.toml
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@ resolver = "3"

[package]
name = "autter"
version = "3.12.0"
version = "3.13.0"
edition = "2024"
default-run = "autter"

Expand Down
Loading