I like running Jasmine with the console open. It gives you insight into various errors that you may not have tests around but may still show up in the console messages. It can detect anything from poorly written tests that fail to run at all to accidentally checked-in console logs.
This approach only works if the console isn’t flooded with useless error messages. If your html has images in it that are normally served by your web server, the images will be fetched and cause 404 messages. You can sometimes get around this by serving up the images in Jasmine or relying entirely on css for your images, but this only works in simple situations. The surefire way to kill these errors is to intercept the image requests and ignore them. If you are using the Jasmine gem, this can be done by adding the following code to your jasmine_helper.rb (not yet tested in Jasmine 2.0)
RubyMine is great for launching focused rspec tests, but is a little trickier for launching Jasmine specs, but we have had it working on my current project using a shell script and RubyMine external tools . The script relies on using sed to parse the first line of your spec file, so this actually only runs the describe block at the top of your file. The steps for our setup below.
Create a shell script somewhere in your project:
Go to RubyMine -> Preferences -> External Tools -> +
This should launch a new tool dialog. Fill in name, descriptions, etc
For program, you should link the script you just created.
For parameters, you should use “$FilePath$”
Bind this external tool under keymaps (look for the name you just gave it). We use command-option-control-f8