v1.7.0

What's Changed

• add error return to Fixture.Start() by @jaypipes in #29
• add custom retry configuration by @jaypipes in #30
• clean up any linter failures by @jaypipes in #31

Full Changelog: v1.6.2...v1.7.0

v1.6.2

What's Changed

• actually write to stdout for Debug() no params by @jaypipes in #25

Full Changelog: v1.6.1...v1.6.2

v1.6.1

What's Changed

• gdtcontext.WithDebug() no args to stdout by @jaypipes in #24

Full Changelog: v1.6.0...v1.6.1

v1.6.0

What's Changed

• add context argument to fixture Stop/Start by @jaypipes in #23

Full Changelog: v1.5.0...v1.6.0

v1.5.0

What's Changed

• uplift Go and Github action runners by @jaypipes in #22

Breaking developer SDK change

This is a breaking change for GDT plugin developers, not GDT users

• rework debug/print into a tracing context by @jaypipes in #21

Full Changelog: v1.4.0...v1.5.0

v1.4.0

What's Changed

• exec: fix debug handler by @jaypipes in #19

Breaking developer SDK change

This is a breaking change for GDT plugin developers, not GDT users

• add context.Context arg to assertions.OK() by @jaypipes in #20

Full Changelog: v1.3.0...v1.4.0

v1.3.0

New features

• Ability to specify none and in for exec plugin's err and out fields (#16)
• Ensure all parse-time errors include line number and column where error was found (#14)

Breaking changes (developer SDK, not gdt test file format)

• The Assertion.Terminal() method has been removed since it was no longer used anywhere (#17)

v1.2.1

Adds more descriptive parse-time errors.

v1.2.0

Support for on.fail field in exec plugin tests (#13)

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:

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.

v1.1.1

Fixes for #7 and #8

Don't add non-Scenario files to Suite and ensure t.Error() is called from sub-test, not scenario