- Bumps version of Jasmine to 3.x
- #201 No longer set Jasmine port using JASMINE_PORT unsupported environment variable.
-
#193 Custom Jasmine Reporters. Contributed by @juanger, this option allows supporting any reports that work with Jasmine. https://github.com/guard/guard-jasmine#custom-report-options
-
#196 Rails 4.2 and Sprockets 3+ support. Fixes bugs with those versions and should set up for the eventual release of Sprockets 4.
-
Bumps recommended version of Jasmine to 2.4, and Guard to 2.1.4
- #161: Jasmine 2.0 support. GuardJasmine now only supports Jasmine 2.0.2 and above via a new Jasmine runner.
- #174 Custom query parameters may be given to the runner.
- #165: Ensure PhantomJS check for a file and not directory. (@jorgemanrubia)
- #154: Run with line number. (@koffeinfrei)
- Upgrade to Guard 2.0
- #152: Change
run_on_change
torun_on_modifications
. (@pjurczynski)
- #145: Exit CLI runner with nonzero exit code when PhantomJS crashes, send empty or invalid response.
- #143: Use Engine initializer to register postprocessor.
- #141: Add JUnit XML output (@edspencer).
- #138: Auto detect Jasmine-Rails server mount option. (@adamstrickland).
- #135: Allows Jasmine to be loaded asynchronously. (@mdeschamps).
- #134: Add config option to customize guard-jasmine's server mount point. (@adamstrickland).
- #133: Remove logger timestamp and severity for
guard-jasmine
CI helper. (@christiannelson).
- Added CLI runner option for setting directory to save coverage reports in. (@michaelcarter).
- #130: Add tilt as dependency (@masarakki).
- Automatic detect Puma as spec server.
- #124: Fix undefined global logs.
- #123: Report javascript errors that prevent specs from running. (@swistak)
- Drop support for Ruby 1.8.7
- #120: Proper spec dir detection when using the Jasmine gem.
- #120: Proper Jasmine URL generation when server is
:auto
and using the Jasmine gem.
- #119: Add a
verbose
option to the CLI runner.
- #118: Fix Rake task execution on Windows. (@twill88)
- #117: Fix load path issues on Windows. (@twill88)
- #116: Actually respect the server timeout option. (@eventualbuddha)
- #112: Faster Jasmine runner exception detection.
- #112: Do not output a failing runner html on startup.
- #111: Configured Guardfile to watch for changes in fixtures directory. (@andyw8)
- #108: Minor cleanups to coverage info. ([@ronen][])
- #109: Add
--coverage-html
and--coverage-summary
support to cli. ([@ronen][]) - #110: Fix coverage hang for large files. ([@ronen][])
- Increase default server and runner timeout.
- #102: Jasmine gem server doesn't respond to
/jasmine
path. - Switch coverage from jscoverage to Istanbul.
- #77: Add coverage support. (@alexspeller)
- #99: Allowed passing custom rackup config via CLI. (@arr-ee)
- Output the runner response body on the CLI when the runner fails to start.
- #90: Fix wrong port in the default Jasmine url.
- #89: Randomize server port if not specified.
- #88: Guard::Jasmine leaves server running on timeout.
- The
:timeout
options takes now seconds and not milliseconds.
- Fix starting the Unicorn test server.
- #85: Improve server timeout handling.
- Fix automatic server detection.
- #84: Fix server start from the CLI.
- Add timeout to the initial server startup.
- #83: Make it possible to run within mountable engine within a dummy app (using jasminerice). (@pschyska)
- #82: Enable the
:auto
server to detection unicorn, thin and mongrel.
- #81: Make the Guardfile template catch
.js.coffee
again.
- #78: Use vanilla JS runner to make it run on Ubuntu 12.04 and PhantomJS 1.4.0.
- #76: Remove nesting limitation on the JSON parser.
- #75: Make sure the server process dies on error. (@mutru)
- Add Guard and cli option to define the number of seconds to wait for the Jasmine spec server to start.
- Remove cli short aliases
-c
,-x
and-f
, use the long form instead.
- #73: Add
:run_all
option to overwrite normal options.
- #72: Add specdoc option to CLI runner. (@robotarmy)
- #71: Add focus option to CLI runner. (@robotarmy)
- #70: Ensure the description is always a String.
- #65: Support unicorn as server. (@pushbang and @clumsysnake)
- Upgrade for Guard 1.1.0
- #64: Suite result specs may be undefined and makes the runner fail.
- #63: The failures are not logged in the right order when there are nested describes.
- #60: Test if spec file exists. (@huyhoang1970)
- #57: Fix error trace notification.
- Add timeout to availability checker.
- The availablity checker prints it's url before starting.
- Change CLI default port to 3001.
- Fix Rake task options.
- PhantomJS 1.5 compatibility.
- Add onError handler for catching PhantomJS errors
- Filter logs and errors depending on the runner setting to speed up result parsing.
- Add errors to the spec doc.
- Fix server start when not running in context of Guard.
- #45: Cannot start Rack server.
- #44: Allow a Guardfile to specify a custom rake task as the server. (@eventualbuddha)
- Optimize PhantomJS runner result passing to improve speed.
- Add a console.log implementation that supports formatting and pretty printing.
- #43: Fix Rake rask for Ruby 1.9.3p125
- #42: Add the possibility to start a custom Rake based server.
- #42: Add option to configure the Jasmine spec directory.
- #41: Clean up Guardfile template. (@DouweM)
- #40: Add clean option to skip the spec path cleaning. (@andersjanmyr)
- Fix broken Rake task.
- #39: Add proper return code for the Rake task.
- #38: Proper server shutdown. (@darrinholst)
- Fix command line version output.
- #36: Fix CLI runner server startup test. (@darrinholst)
- Clean paths after last failed specs have been added.
- #31: Don't try to stop a server when no server is running.
- #30: Provide a Rake task that wraps the Thor CLI.
- #28: Relax gem dependencies.
- Improve spec file inspector.
- Switch to ChildProcess for managing the servers.
- #21: Remove version from Rack and Thor dependencies.
- Avoid log output from the server in the console
- Add Mongrel and Thin as servers.
- #17: Fix CI helper for Bundler 1.1. (@darrinholst)
- #16: Allow the server env to be configured in the CI helper. (@mkdynamic)
- Set server env as default back to development for better debugging.
- Add
:server_env
option to set rack environment. - Fix JSON decoding problem.
- #10: Add
.coffee
to the allowed file types in the inspector. - #9: Autodetect PhantomJS location. (@dnagir)
- #12: Fix timeout in the PhantomJS runner.
- #8: Update README with quicker setup instructions for Rails 3.1. (@dnagir)
- #11: Improve default Guardfile definition. (@dnagir)
- Set port on the default jasmine_url.
- Automatically start either a Rails or Jasmine Gem server.
- Rethrow SystemExit in spec run for proper exit status.
- Add cli helper to run guard-jasmine on CI server.
- Quote spec runner suite argument.
- Add
:timeout
option.
- Ensure console.log capturing before the spec run is ignored.
- More robust error handling..
- Change default Jasmine url to http://localhost:3001/jasmine
- Add
:focus
option. - Add
:console
option. - Ensure PhantomJS bin is available in the right version.
- Disable :task_has_failed until new Guard version is available.
- Make use of :task_has_failed to abort Guard groups.
- #3: Correct :jasmine_url in README.md (@dnagir)
- Improved formatting.
- Add an executable to request the results from the command line.
- Never run a old failed spec when only invalid paths are passed.
- When the inspector finds spec/javascripts, it only returns this path.
- Introduce
:max_error_notify
to limit error system notifications.
- Multiple enhancements for phantom spec runner
- Format known error message styles for better readability
- Fix url to Jasmine runner for a single suite.
- Better system notifications
- Catch connection refused from the Jasmine availability check.
- Test if Jasmine runner is available on start.
- #1: Fix filter Regex.
- Ensure the console.log output in the test won't go to the JSON result.
- Do not pass the spec dir through the Inspector.
- Add
:all_on_start
option. Run all
triggers all specs at once, not all specs sequentially.
- Fix inspector glob to get also non-coffee specs.
- Finish the runner phantomjs bridge.