Make runner methods chainable.

[jamestalmage]

This flattens the entire runner.tests data structure into a single array.

Elements of the array are then chosen using runner.select(selectorObject).

The selector currently just compares its own properties to each test, and selects those that have matching properties. It will be easy to expand with groupMembership queries, etc.

[jamestalmage]

TODO: We probably should look in to replacing some of these polyfills with core-js equivalents. Hopefully cutting down on duplicate downloads for users.

[jamestalmage]

I'm getting close to turning this into some cool chaining functionality.

only.serial(...)
serial.only(...)
skip.serial(...)
afterEach.skip(...)
...
etc.

I need sleep now though. More tomorrow.

[sindresorhus]

I like where this is going :)

Chaining is an important step as it will let you skip a test without losing the type of test. Right now you can't have a skipped test that is serial. You have to remove the serial part, which loses some important information.

[jamestalmage]

OK - saw my error - chaining should now work.

This needs some cleanup (see the various TODO's), documentation, and more test coverage.

I should be able to wrap it up this weekend.

When it comes time to make nested groups, we will continue along the same pattern here, but replacing the base _addTest with one that merges the group settings as well (so you can skip an entire group, or set serial as the default for a group for example).

I also need to add the inverse of most of the boolean flags. (i.e. concurrent = {serial: false}). That would be used for making a few tests concurrent in a group of tests where the default is serial.

In all, I think doing it this way is going to open up some really cool stuff.

OK - bedtime for real now.

[jamestalmage]

I am starting to think all these flags belong on a metadata object, i.e.:

test.skipped => test.metadata.skipped
test.exclusive => test.metadata.exclusive

Otherwise we need to always be careful the metadata properties never share a name with a useful property. (For example we can not use test.skip as the metadata property, because test.skip() is the method that sets that flag).

[jamestalmage]

Otherwise we need to always be careful the metadata properties never share a name with a useful property

Useful properties are going to be hard to predict as well, especially once we enable custom assertions.

[sindresorhus]

Just put the filter function inline.

[jamestalmage]

Wish I could use arrow functions 😞

[sindresorhus]

@jamestalmage Reviewed. This looks very good. Could you update the readme about the methods being chainable?

[vadimdemedes]

I don't really understand the point of Hook class, since it returns a Test instance in test method. @jamestalmage Could you please explain?

Otherwise, I really like the idea behind this PR.

[jamestalmage]

It's for beforeEach / afterEach. Which need to be created multiple times. It's just storing the constructor args for later invoke (multiple times)

[vadimdemedes]

@jamestalmage makes sense!

[sindresorhus]

👍 Landed. Superb work on this one @jamestalmage :)