Support taking arbitrary actions upon test failure #12
Assignees
Labels
enhancement
New feature or request
Comments
jaypipes
added a commit
that referenced
this issue
Aug 8, 2023
Users would like to be able to execute commands, collect log
information, grep for errors in output and other actions when a test
assertion fails.
For instance, if an application is deployed using Kubernetes and network
connectivity doesn't work for the application, the test author might
want to call kubectl logs in the event of a test failure.
Another example might be if you wanted to grep a log file in the event
that no connectivity on a particular IP:PORT combination could be made
you might do this:
```yaml
tests:
- exec: nc -z $HOST $PORT
on:
fail:
exec: grep ERROR /var/log/myapp.log
```
The grep ERROR /var/log/myapp.log command will only be executed if there
is no connectivity to $HOST:$PORT and the results of that grep will be
directed to the test's output. You can use the gdt.WithDebug() function
to configure additional io.Writers to direct this output to.
This patch adds support for the exec plugin's `on.fail` field, hopefully
in a way that is extensible for other plugins to use as an example (and
possible embed the `plugin/exec.Action` struct).
Addresses Issue #12
Signed-off-by: Jay Pipes <[email protected]>
|
Still need to implement this for the HTTP and Kube plugins. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Users would like to be able to execute commands, collect log information, grep for errors in output and other actions when a test assertion fails.
For instance, if an application is deployed using Kubernetes and network connectivity doesn't work for the application, the test author might want to call
kubectl logsin the event of a test failure.Another example might be if you wanted to grep a log file in the event that no connectivity on a particular IP:PORT combination could be made you might do this:
The
grep ERROR /var/log/myapp.logcommand will only be executed if there is no connectivity to $HOST:$PORT and the results of that grep will be directed to the test's output. You can use thegdt.WithDebug()function to configure additionalio.Writers to direct this output to.The text was updated successfully, but these errors were encountered: