0c4113e167
Quick fix - Spec needs j$ at execute time
2013-10-02 22:45:33 -07:00
a563e67015
Move selenium_runner.yml to spec/javascripts/support
...
- The selenium runner gem should support configurable path as the main
gem does so we don't need to do this. This workaround is kind of
gross.
2013-10-02 16:48:13 -07:00
fab489851e
Fix paths for node specs
...
[#58126010 ]
2013-10-02 16:41:07 -07:00
1c19b8e38a
Move spec files back out of spec/javascripts
...
- Jasmine gem allows us to specify a path to jasmine.yml via ENV
[finish #58126010 ]
2013-10-02 16:32:35 -07:00
fc258b3d36
Make it easy to copy the title of failing specs
...
[finish #58121820 ]
2013-10-02 15:14:41 -07:00
ffa6138d75
Make getGlobal() work in strict mode
...
An update of https://github.com/metaweta/jasmine/commit/fb3e1acb09b4dbb9ccdbc15ce64b4a0e471f4541
ES5 strict mode does not promote an undefined 'this' to the global object. The only way to get the global object in strict mode is to say 'this' while in the global scope.
2013-10-02 12:38:25 -06:00
51dd66a4cc
Turn the exceptions spec back on, it still works
2013-10-02 10:24:24 -07:00
37a3135d6a
cleanup whitespace
2013-10-01 16:30:17 -07:00
cb8ba74937
Don't add periods to the full name of a spec
...
- Breaks links for spec filters
- Looks strange if users add their own
[fix #58043244 ] fix #427
2013-10-01 16:28:33 -07:00
70fb0f0ed5
Update Firefox pretty print test
...
At some point, firefox changed the exception message.
2013-09-30 15:43:44 -07:00
15889494c5
Update node suites to not rely on previous accidental global j$ and create its own
2013-09-29 14:59:58 -07:00
da33c7823e
Add missing var in front of j$ to avoid polluting global namespace
...
Users should only have 'jasmine' in global namespace, j$ should be
fully internal unless developing for jasmine
As brought up by Morten Maxild
2013-09-29 14:46:55 -07:00
04e1d8420e
Ensure tunnel_identifier is properly quoted for travis builds
2013-09-25 14:24:57 -07:00
19b2472761
Really make tunnel_identifier a string.
...
yay.
2013-09-25 11:24:41 -07:00
1fc614ad19
Tunnel identifier must be a string
...
- Travis provides a float.
2013-09-25 11:03:45 -07:00
84692f545c
Use jasmine_selenium_runner to run specs via Sauce
2013-09-25 10:45:53 -07:00
5017d1a4f1
Make rake jasmine:ci run specs correctly.
...
- Will replace rake core_specs.
- Remove obsolete dependencies & files -- most of these were for build tasks we
are no longer using. Notably, rspec and spec_helper were deleted.
2013-09-25 10:11:02 -07:00
963cd5e850
Make rake dev dependency
2013-09-24 11:31:21 -07:00
527394068e
Update specs to use new HTTP Runner interface.
2013-09-24 11:30:50 -07:00
5e279a1393
Remove unnecessary Jasmine.configure.
2013-09-20 11:16:40 -07:00
8f0f0a607e
update self test to work with gem runner interface
2013-09-20 11:09:35 -07:00
4891d578e3
Set default rake task
2013-09-19 10:15:15 -07:00
efc384c6d6
Allow Env to take optional spec/suite ids when asked to execute
2013-09-17 19:55:49 -07:00
d60786a06c
More clearly differentiate between spec and suite ids
2013-09-17 19:55:48 -07:00
66010d01ec
Give reporting symbols a little bit more height
...
Ensures they don't appear cut off when in the last row
2013-09-16 21:05:24 -07:00
1619067ddd
Merge pull request #428 from tjgrathwell/htmlreporter-inline-block-dots
...
Change HTMLReporter symbols to be inline-block instead of floated
2013-09-16 20:55:49 -07:00
79a75f5bdb
HTMLReporter symbols are inline-block rather than floated
...
On a very large test suite (8000 specs), a significant amount
of time is spent just drawing the spec dots. Some sort of
worse-than-linear artifact that summons itself only when you
have 8000 floated elements trying to hang out together.
This performance penalty is not seen with inline-block.
In Chrome 29:
Floated dots: 16.795s
Inline-block dots: 2.774s
Setting the dots to 'display: none;' takes about the same time
as the inline-block figure, so this is probably a low enough bound
(no need for chunked rendering or who knows what).
2013-09-10 19:46:51 -07:00
7158e048a6
Update Jasmine CSS build process
...
- Update compass configuration to build jasmine.scss into lib
- Remove src/html/jasmine.css (since jasmine.scss builds directly into
lib now)
- Bump lib/jasmine-core/jasmine.css to be latest from scss
2013-09-09 21:41:24 -07:00
f8f064d12d
Update jasmine-performance.yml
...
Get it back into working condition and more similar to jasmine.yml
2013-09-09 21:41:24 -07:00
8ac085c103
Use jasmine.DEFAULT_TIMEOUT_INTERVAL for async timeout
...
Allows a user to specify their desired timeout interval for async specs
and change it on a per spec basis (for particularly slow specs, for example).
As pointed out by @Eric-Wright in #422 . [finishes #55996798 ]
2013-09-08 21:41:45 -07:00
03dfea967c
Remove unused jasmine.DEFAULT_UPDATE_INTERVAL
2013-09-08 14:18:34 -07:00
f463e1f7aa
Consistent 'this' between befores/it/afters
...
Change the 'this' user functions are called with to be an empty object
instead of the QueueRunner so that if the user puts properties on it,
they won't conflict.
Also, changes async specs to be called with a proper 'this', as pointed
out by @Eric-Wright in #419 and #420 .
[finishes #56030080 ]
2013-09-07 18:28:03 -07:00
4bff199c2a
Rename a spy's callReturn and callThrow
...
.and.callReturn is now .and.returnValue
.and.callThrow is now .and.throwError
[finishes #56281634 ]
2013-09-06 21:55:14 -07:00
e3f0389ac2
Change andThrow to always throw an Error
...
If an error is passed in, it is thrown, otherwise the argument passed
in is wrapped in an Error
[finishes #50607615 ][closes #372 ]
2013-09-05 23:05:45 -07:00
be0f7b4117
EnvSpec for timing out async spec fix
...
Spec still can't work for maximumSpecCallbackDepth = 1 until further
mock clock enhancements. Fixes the specs running twice issue caused by
the previous commit.
2013-09-02 21:48:44 -07:00
edb46a6f7c
Fix spec in EnvSpec.js for specs that hang
...
This spec would hang when maximumSpecCallbackDepth was set to 1
[Fixes #54168730 ]
2013-09-02 20:39:37 -07:00
a442acb8aa
Mock Clock now correctly schedules delayed functions during a 'tick'
2013-09-02 18:50:17 -07:00
fc409f39a1
Workaround and bug exposure for IE8 and PrettyPrinter, which doesn't work well when trying to pretty print the native timer functions on IE. Make Jasmine's suite green and call out for a fix once we re-write the pretty printer. [Finishes #54168708 ]
2013-09-01 15:38:14 -07:00
ba55cb5e38
Mock clock now less intrusive, replacing global timer funcions only when clock is installed. [ Fixes #54168708 ]
2013-08-27 22:46:01 -07:00
2d4f398dd6
Merge branch 'master' of https://github.com/pivotal/jasmine
2013-08-27 22:43:06 -07:00
5ba6e51e1c
Restore custom failure messages for toHaveBeenCalledWith
...
As pointed out by @tjgrathwell
2013-08-26 23:24:43 -07:00
ba43e37356
Updating GOALS doc after rc2
2013-08-06 08:04:37 -07:00
0f42f2709a
Update PrettyPrinter to better check for an Object
...
Includes test case to fix FF as suggested by @ondras
Fixes #409
2013-08-03 11:49:20 -07:00
4c4317b80e
Update BrowserFlags to include Firefox
...
- DRYs up the browser checking code
- Adds in Firefox as another flag
- Makes it possible to do checks like `if (env.ieVersion)` to target all
IE versions
2013-08-03 11:45:13 -07:00
b4bb99dfdf
Merge pull request #410 from martyhines/fix-broken-link
...
Updated contribute.markdown links
2013-07-31 07:54:42 -07:00
d721418490
Updated contribute.markdown links
2013-07-31 10:40:28 -04:00
45fd8df861
Adding ignores for latest RVM/RbEnv convention
2013-07-30 08:08:24 -07:00
0e800ee243
Rename to GitHub convention; Makes this doc available during pull request creation
2013-07-30 08:07:22 -07:00
8a8cc03dea
Add release notes & GitHub releases instructions
2013-07-28 20:59:57 -07:00
be0e6222c5
Bumping to 2.0.0-rc2 due to an old, yanked 2.0.0-rc1
2013-07-28 17:55:29 -07:00
Davis W. Frank