Writes tests: a census of 126 listings

Tests here mean workflow acceptance and evaluation cases for the agent, not unit tests written into a client's repository.

Source retrieved 2026-09-09

Test writing is a prompt-level behaviour of the coder persona pinned to Vitest conventions, not a separate test-generation tool or package on the sheet.

Source retrieved 2026-09-09

The documented Verify stage runs the repository's existing gates; test authoring appears only in the example prompt, not as a capability claim.

The vendor publishes a worked transcript of aider authoring a black-box unit test from the repository map alone, without the source of the function under test in context.

Source retrieved 2026-09-09

It generates test cases, but conversational ones: the documented Test Suite turns historical requests and knowledge-base articles into replayable cases that check agent behaviour, not unit tests for source code.

Source retrieved 2026-09-03

The vendor's own best-practice sequence is to have the agent author a test block before implementing, then run the suite to verify its change.

Source retrieved 2026-09-10

Agent generates unit tests for new code; the legacy-migration workflow adds tests as part of each module PR.

Source retrieved 2026-09-02

Testing is described as a quality-assurance stage their team performs before launch; nothing says a test suite is written for or handed over to the client to run afterwards.

Source retrieved 2026-09-11

It generates and runs call-scenario suites with assertions against the agent, including scenarios derived from historical transcripts; these are conversation tests, not unit tests for code.

Tests are evals: automated conversation tests of agent behaviour, run by the adk CLI. The adk-evals skill writes them, and there are no unit tests over source code.

Source retrieved 2026-09-02

The agent-loop walkthrough has the agent updating and re-running a project's tests alongside its edits.

Source retrieved 2026-09-02

Writes tests for untested code as a named use case, and runs them as part of the same task.

Source retrieved 2026-09-02

Test authoring is a named use case, covering unit and integration tests for existing large codebases rather than only tests for code it just wrote.

Source retrieved 2026-09-12

Unit test generation is a Team-and-above finishing touch, absent from the entry Essentials plan, and is itself labelled open beta on GitHub, GitLab and Azure DevOps.

Source retrieved 2026-09-15

Documented CLI workflow for writing a unit test for a named function.

Source retrieved 2026-09-02

It generates and runs happy-path and failure-path scenarios against each integration before the assistant may call it; these are vendor-run integration checks, not a test suite you own or edit.

Source retrieved 2026-09-12

Cresta generates test cases and LLM evaluators for agent behaviour from production traffic and documentation; these are conversation tests, not software unit tests.

Source retrieved 2026-09-02

Test generation is named as agent work, and Automations can be configured to add tests on every new commit.

Source retrieved 2026-09-02

Analyses the repository's existing test style and writes additional tests to raise coverage.

Source retrieved 2026-09-02

The only test-writing claim describes cloud Devin sessions delegated from a Space; no equivalent statement is made for the local agents.

Source retrieved 2026-09-03

The /install-qa skill generates QA sub-skills and executes end-to-end test flows per diff, with evidence.

Source retrieved 2026-09-02

Test generation is one of the prebuilt smart actions in the IDE, and the overview lists unit-test generation as a chat capability.

Source retrieved 2026-09-02

Testing is named as a step the agent performs on what it builds; nothing on the site says it authors a test suite or runs your project's existing tests.

Source retrieved 2026-09-15

Test work is a named cloud-agent task, and the agent runs the tests it writes in its own ephemeral environment.

Source retrieved 2026-09-02

Test changes appear in the vendor's own agent example output; no dedicated test-generation feature is documented.

What it generates are agent evaluation sets captured from real sessions, not unit tests; the evaluation tooling is documented as Python-only, so other language bindings do not get it.

Source retrieved 2026-09-15

Test generation is not native: goose produces Playwright specs only after you install the third-party Playwright CLI agent skill plus Node and the Summon extension, and the docs show it writing browser tests rather than unit tests.

Source retrieved 2026-09-16

Runs code and tests as part of a task and verifies the result; plan mode produces an explicit test strategy and test cases.

Source retrieved 2026-09-02

Test writing is named as part of the SDLC coverage Kilo sells to enterprises.

Source retrieved 2026-09-02

Engine generates evals and datasets rather than unit tests, and the row is checked only for Plus and Enterprise.

Source retrieved 2026-09-02

Vendor claims agents run test suites; it never claims they author tests.

QA agents exercise the app in a browser; the vendor never claims it produces test code you keep

Claims it tests the app it just generated; no claim that it authors test code or a test suite.

Source retrieved 2026-09-02

Evaluations auto-generates and runs structured test cases against an agent workflow with literal or fuzzy expected results; these are agent evaluations, not unit tests for application source code.

Source retrieved 2026-09-02

Adding a regression test is given as a sandbox multi-step workflow example; no dedicated test-generation feature is documented. The SDK's own testing utilities test agent workflows, not application code.

Source retrieved 2026-09-02

Test generation and coverage expansion is a named workflow; a separate QA agent also exercises the running software rather than the test suite.

Source retrieved 2026-09-02

It authors and maintains conversation simulation tests that run in CI; these are agent scenario tests, not unit tests for source code.

Source retrieved 2026-09-02

Replit says Agent tests the app it builds by driving a real browser; it never claims Agent authors test code or a test suite.

Source retrieved 2026-09-02

Produces graded conversation test cases for its own agents, not software tests.

Testing here is pre-launch acceptance testing of agreed workflows and fallback paths, not authored automated test suites handed to the client.

Source retrieved 2026-09-04

Apex test classes and LWC Jest tests are generated alongside the code, with a dedicated QA Validator sub-agent for coverage.

Source retrieved 2026-09-03

Conversation and voice simulations are generated and run on every agent build, and Agent Studio keeps them as a regression suite; these test agent behaviour, not your code.

Source retrieved 2026-09-03

Builds are exercised with sample data and a staging run before launch, and trading work adds automated walk-forward validation, but no automated unit or regression test suite is promised as a deliverable.

Source retrieved 2026-09-12

It ships an evaluation harness rather than a test writer: evals score agent outcomes against ground truth before deploy and Optimize proposes changes, but you author the eval sets and none of this produces unit tests for a codebase.

Source retrieved 2026-09-03

A dedicated unit-test task writes tests against the uploaded code and runs them where the environment allows.

Source retrieved 2026-09-03

Test authoring is named only as a task delegated to a connected third-party coding agent; there is no test-writing skill of Vellum's own in the skills catalog.

Source retrieved 2026-09-03

Test authoring is one of the vendor's enumerated coding capabilities, and the agent can run the test it wrote inside a REPL session.

Source retrieved 2026-09-03

Writing tests is named as a first-class task type, and after each task Zenflow runs the repository's own linters, type-checkers and test suites as verification.

Source retrieved 2026-09-09

Test authoring appears only as an example task for a swarm sub-agent; there is no test-generation feature in the tool set or the docs.