return the created test in xit for bdd interface

[Bamieh]

Description of the Change

Fixes #3142

The bigger reason for this fix is to ensure consistency across across both active and pending tests (ie it and xit).

I've also added a test suite for setting timeout by appending it to test

Alternate Designs

We can also remove the return statement to disable this feature in the bdd interface, but i personally favor having it around, maybe even document it after adding some more test cases!

Benefits

Since @boneskull does not encourage the use of the this keyword in writing tests, documenting this change might create a shift to increased usage of arrow functions and less usage of this.

Applicable issues

patch

[coveralls]

Coverage remained the same at 89.95% when pulling 36a2f1f on issue/3142 into 5fbbce9 on master.

[coveralls]

Coverage remained the same at 89.95% when pulling 7b82003 on issue/3142 into 5fbbce9 on master.

[boneskull]

test failure on AppVeyor is curious

[boneskull]

@Bamieh it's helpful to write "closes #xxxx" in the commit message somewhere as it will automatically close the associated issue upon merge, as well as link the commit to the issue (#3143)

[boneskull]

we're seeing a seemingly random npm failure under Node.js v4, so I'm upgrading to npm v5.6.0. If this fails I'll create npm-debug.log as an artifact and try to get more info...

[coveralls]

Coverage remained the same at 89.95% when pulling e227a78 on issue/3142 into 5fbbce9 on master.

[boneskull]

saucelabs flake? really? at least it's flake I haven't seen before. retrying