v1.1.0

New functionality

Skip scenario if condition true (gdt-dev/gdt#5)

Adds the ability to skip a test scenario if a condition evaluates to true. Use the skip-if field in the Scenario YAML to tell gdt to skip the scenario if that condition evaluates to true. The condition is just a test.

For example, let's assume you have a gdt-kube scenario that looks like
this:

tests:
 - kube.create: manifests/nginx-deployment.yaml
 - kube:
   get: deployments/nginx
   assert:
     matches:
       status:
         readyReplicas: 2
 - kube.delete: deployments/nginx

If you execute the above test and there is already an 'nginx'
deployment, the kube.create test will fail. To prevent the scenario
from proceeding with the tests if an 'nginx' deployment already exists,
you could add the following

skip-if:
 - kube.get: deployments/nginx
tests:
 - kube.create: manifests/nginx-deployment.yaml
 - kube:
   get: deployments/nginx
   assert:
     matches:
       status:
         readyReplicas: 2
 - kube.delete: deployments/nginx

With the above, if an 'nginx' deployment exists already, the scenario
will skip all the tests.

Breaking changes in YAML definitions

exec plugin assertions now under assert field (gdt-dev/gdt#6)

The exec plugin now nests its assertions under an assert field.

So, instead of this:

tests:
 - exec: echo cat
   out:
     is: cat

you now do this:

tests:
 - exec: echo cat
   assert:
     out:
       is: cat

require renamed to fixtures (gdt-dev/gdt#2)

The require field in the Scenario YAML definition has been renamed to the more appropriate fixtures, since this field lists the fixtures that the scenario requires.

kube plugin assertions now in assert field

The kube.assert field in the kube plugin's Spec YAML definition has been renamed to the shorter assert, matching both the exec and http plugin.