Handles the whole task
Identifies observable behavior, boundaries, invariants, error paths, dependencies, fixtures, and project conventions before writing tests.
Identifies observable behavior, boundaries, invariants, error paths, dependencies, fixtures, and project conventions before writing tests. The Agent prepares meaningful unit tests that fit the codebase and keeps the evidence and open questions clear for review.
Provide code, schemas, requirements, or examples and explain the audience, decision, constraints, and definition of done.
Identifies observable behavior, boundaries, invariants, error paths, dependencies, fixtures, and project conventions before writing tests.
Review meaningful unit tests that fit the codebase, resolve marked questions, and ask for changes in the same conversation.
Identifies observable behavior, boundaries, invariants, error paths, dependencies, fixtures, and project conventions before writing tests.
Tests are run when possible; failures, environment limits, uncovered paths, and brittle assumptions are reported.
Continue in the same conversation to change the scope, emphasis, format, or level of detail in meaningful unit tests that fit the codebase.
Start with code, schemas, requirements, or examples. Add the audience, decision, constraints, preferred format, and anything that must remain unchanged.
Identifies observable behavior, boundaries, invariants, error paths, dependencies, fixtures, and project conventions before writing tests.
Tests are run when possible; failures, environment limits, uncovered paths, and brittle assumptions are reported.
Yes. Keep working in the same conversation to revise meaningful unit tests that fit the codebase, answer open questions, or change the audience and format.
Keep working with the same material without moving it between separate products.
Use Vecbase for test case generator. Give the Agent your context, check the evidence, and refine a risk-based test case set.
Use Vecbase for api documentation. Give the Agent your context, check the evidence, and refine accurate API documentation developers can use.
Use Vecbase for code explainer. Give the Agent your context, check the evidence, and refine a clear explanation of how the code actually works.
Vecbase
For Unit Test Generator, add code, schemas, requirements, or examples, explain what matters, and let the Vecbase Agent prepare meaningful unit tests that fit the codebase you can review and refine.