When there are zero steps in a file (as can happen when excluding
certain tags in a test run) it attempts to close the driver, having
never created it in the first place.

For some reason, certain commands are not failing
leaving the scenario running for ever, causing our
test runs to hang. The old version of selenium does
seemingly not have this problem.

Multiple tags should be supplied in multiple --tags arguments,
which allows logical ORs and ANDs to be applied to tags. This
creates --tags arguments according to the cucumber docs:

https://github.com/cucumber/cucumber/wiki/Tags

tags: ['@one', '~@two'] will run scenarios with tag @one, but not
scenarios with tag @two.

Fixes mojotech#202

0.3.2 was accidentally unpublished from npm can cannot be re added!

Probably gives no benefit
We're moving to node6, and the fixed dependencies might be causing issues

This reverts commit 26eebc6.

Sticking with node 0.12 for now, so put the shrinkwrap back