Closed defrex closed 9 years ago
What version(s) of jasmine are you running (both the jasmine
gem and jasmine-core
)? Do you have an example suite that exhibits this behavior?
The jasmine gem should be serving exactly the same javascript for both the normal server
task as well as the ci
task. We do have a story in tracker to make it so that global beforeAll
and afterAll
can support expectations that might fix your problem if you are doing that.
After a bunch more digging, this turned out to be the issue with PhantomJS not supporting bind.
That said, ideally JS errors outside of specs would trigger a test failure in the CI runner. I had to run Phantom with remote debugging turned on to figure this out.
When I run
rake jasmine
and request the resulting server, my tests run without issue. However, when I runrake jasmine:ci
there is no error, but also no tests are run: "0 specs, 0 failures".I threw a breakpoint in
Jasmine::CiRunner
so I could request the same URL as phantom (from Chrome). It runs one test (which passes), then errors out with the following: