Filter integration tests from npm command

[jbudz]

This lets you npm run test:ui -- --grep=foo instead of running the intern bin directly. I didn't add functionalSuites because it needs the main index file for babel transpilation now.

edit: added functionalSuites for api tests, and an 'apps' filter too.

Using grep alone will not prevent the before block of every test from running, so it can be useful to filter by suite. Currently, filtering tests by suite doesn't work because tests are all loaded together, ran through babel, and then passed in as one suite. This allows us to filter test runs by application.

Usage:

npm run test:ui -- --appSuites=management,status

and with grep:

npm run test:ui -- --appSuites=management --grep=initial\ state
...snip
>> 0/23 tests failed (18 skipped)

An alternative is to split tests back out into individual suites and run each suite through babel, but that adds some boilerplate to each test.

[LeeDr]

The problem with using grep to run specific tests is that it still runs the before, beforeEach, after, and afterEach methods of every test. While this cuts some time off running without the grep, it's not really a good solution.
That's not to say we shouldn't do this PR. Only saying that we still don't have a decent solution for running individual test suites.

Naming wise, I'm referring to the 'visualize app tests' vs. the 'area chart test suite' which contains several tests as an example. We should be able to run one suite, but not individual tests within a suite because they are not all atomic (it would be too slow to get through the tests if they were).

[LeeDr]

LGTM

[Bargs]

Awesome 💯

[scampi]

thanks @jbudz this will help greatly!