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:
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).
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:
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 theplugin/exec.Action
struct).Addresses Issue https://github.com/gdt-dev/gdt/issues/12