feat: undeprecate "specs" in package.json

[noomorph]

Description:

In [email protected] there was a premature deprecation of "specs" property in detox section of package.json. It appeared inconvenient for anyone who prefers terse commands like detox test over verbose detox test e2e. From now on, "specs" property will act as a fallback if a specific test folder has not been specified. For example (1):

detox test   # translates to: mocha <...args> e2e
detox test e2e/01.sanity.test.js  # translates to: mocha <...args> e2e/01.sanity.test.js

For the reference, previously it used to work like (2):

detox test   # translates to: mocha <...args> e2e
detox test e2e/01.sanity.test.js  # translates to: mocha <...args> e2e e2e/01.sanity.test.js

The problem of the latter was that you could not focus (override defaults) on a specific test file without having to use specs in package.json and deprecated --specs in the command line (3):

detox test --specs e2e/01.sanity.test.js  # overrides specs in package.json
# mocha <...args> e2e/01.sanity.test.js

Since (2) has been introduced very recently and did not function well, I suggest to consider this rather a minor version than a breaking change.

Your considerations are welcome.

P. S. As for file deprecation warning, it has been reworked and looks like on the screenshot:

[LeoNatan]

Any luck finding why it showed an unrelated error when specs was not provided?

[noomorph]

@LeoNatan, yes, it was a bug in mocha@^5.0.0. After upgrading to mocha@^6.0.0, that weird error has disappeared, now it is comprehensible:

[noomorph]

@LeoNatan, as far as I understand, it is a synergy of those pull requests that resolved the weird error:

mochajs/mocha#3650
mochajs/mocha#3654
mochajs/mocha#3692

The mocha contributors have fixed a lot of command-line interface errors, as can be seen in their CHANGELOG.