Elaborate on vague errors

[andresn]

Hi Arrow team, I would say this is a high impact pain point that impedes adoption. To replicate, add any syntax error to your YUI Test file, or descriptor. The error log will convey vague errors such as:

[2014-03-31 13:04:58.606] [ERROR] TestSession - Error while running controller :Scenario failed at atom: 1
Error :UnknownError: unknown error: Runtime.evaluate threw exception: SyntaxError: Unexpected token .
(Session info: chrome=33.0.1750.152)
(Driver info: chromedriver=2.9.248307,platform=Mac OS X 10.9.2 x86_64) (WARNING: The server did not provide any stacktrace information)
Command duration or timeout: 13 milliseconds

Or:

[2014-03-31 13:04:58.606] [ERROR] TestSession - Error while running controller :Scenario failed at atom: 1

(respectively).

This is particularly problematic when front-loading markup testing to a descriptor file. A few solutions off the top of my head:

1. Identify wrapper points for try and catch statements within Arrow layers.
2. Json Lint / JSHint descriptor file come runtime.