jasmine-node exits with no output on a bad URL

[andyshinn]

We ran into an issue when writing some tests where jasmine-node was actually just exiting with 0 even though nothing was happening! It turns out, one of the URLs in our frisby test was bad. Here is an example:

var frisby = require('frisby');

frisby.create('We should be able to GET a URL')
  .get('https://googlenotreally.com')
  .expectStatus(200)
  .toss();

When run with jasmine-node --verbose, this silently exits with 0. The working URL outputs the test and passes normally:

var frisby = require('frisby');

frisby.create('We should be able to GET a URL')
  .get('https://google.com')
  .expectStatus(200)
  .toss();

I'm running with frisby@0.6.8 and jasmine-node@1.10.2.

Surely, the test with the bad URL should fail instead of exit cleanly. Any ideas what might be happening?

[andyshinn]

I notice that it fails in method this.current.it with the following error:

[Error: Destination URL may be down or URL is invalid.
Trying: 'GET https://googlenotreally.com'
Got: 'Error: getaddrinfo ENOTFOUND'
]

[vlucas]

Interesting. I know it's throwing that Exception, because I fixed it at some point, but it looks like it's getting trapped somewhere else. I'll investigate this further.

[vlucas]

This has been fixed in v2. Please update.