It seems that if there is a problem instrumenting files, the only error message reported is:
Warning: PhantomJS timed out, possibly due to an unfinished async spec. Use --force to continue.
to make matters more difficult, the specrunner.html file that gets generated will not display any errors at all unless Raise Exceptions is set to true. And even then, all I get is:
TypeError: this.expectationResultFactory is not a function
Which doesn't help me at all.
Now, all of this is down to configuration problems. However, what was problematic for me is that my Gruntfile is quite large and so sometimes it's not always easy to spot the fact that I missed something. And as the error message that ultimately gets reported to me by Grunt either locally or by the CI server is that it's possibly due to an unfinished async spec, the first thing I (and I'm sure many others) did was to check all my tests. In a large project, this is time consuming.
It seems that if there is a problem instrumenting files, the only error message reported is:
to make matters more difficult, the specrunner.html file that gets generated will not display any errors at all unless Raise Exceptions is set to true. And even then, all I get is:
Which doesn't help me at all.
Now, all of this is down to configuration problems. However, what was problematic for me is that my Gruntfile is quite large and so sometimes it's not always easy to spot the fact that I missed something. And as the error message that ultimately gets reported to me by Grunt either locally or by the CI server is that it's possibly due to an unfinished async spec, the first thing I (and I'm sure many others) did was to check all my tests. In a large project, this is time consuming.
Example failing project: https://github.com/alex-dow/istanbul-error-reporting-test