You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat(runner): add support for running and repairing tests
This commit introduces the ability to run tests against the generated code as part of the evaluation process.
A new optional `testCommand` can be in the environment configuration. If provided, this command will be executed after a successful build.
If the tests fail, the tool will attempt to repair the code using the LLM, similar to how build failures are handled. The number of repair attempts is configurable.
The report has been updated to display the test results for each run, including whether the tests passed, failed, or passed after repair. The summary view also includes aggregated statistics about the test results.
Copy file name to clipboardExpand all lines: docs/environment-reference.md
+5Lines changed: 5 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -179,3 +179,8 @@ Defaults to `<package manager> run build`.
179
179
180
180
Command used to start a local dev server as a part of the evaluation.
181
181
Defaults to `<package manager> run start --port 0`.
182
+
183
+
### `testCommand`
184
+
185
+
Command used to run tests against the generated code. If this property is not provided, tests will not be run. The command should exit with code 0 on success and a non-zero exit code on failure. The output from the command (both `stdout` and `stderr`) is captured and used for repair attempts if the tests fail. The test command will time out after 2 minutes.
0 commit comments