Fix #564: Fix tests not running due to Espree bump

[jfmengels]

Fix #564: Fix tests not running due to Espree bump.

I changed the tests to use babel-eslint, because they are now invalid with Espree 3.2.0.
One of the tests didn't work correctly with both parsrs, so I just disabled it.
Blocks #555

cc @ljharb

[coveralls]

Coverage decreased (-0.1%) to 97.697% when pulling 863de65 on fix-parser-tests into 515d159 on master.

[ljharb]

LGTM! thanks :-)

[ljharb]

@benmosher ping, it'd be nice to merge this ASAP to unbreak master

[benmosher]

I want to take a closer look at this. The tests run with Espree because it's the default parser; I'm not comfortable just changing it to sate Travis without better understanding why they're failing.

All the post-ES2015 ones should have been using Babel already, so what would change in Espree to break the valid ES6 ones?

[benmosher]

(taking a look now)

[benmosher]

I updated the broken test. Though I guess the message changed because babel-eslint reports the error differently.

I'll merge once it goes green?

[coveralls]

Coverage remained the same at 97.837% when pulling a1386ee on fix-parser-tests into 515d159 on master.

[coveralls]

Coverage remained the same at 97.837% when pulling a1386ee on fix-parser-tests into 515d159 on master.

[benmosher]

@ljharb you may fire when ready