Jasmine Core 2.4.0 Release Notes
Summary
This release contains a number of fixes and pull requests. The most notable is probably that Jasmine now supports randomization of spec order
Changes
- Run jasmine’s specs in random order
- Add support for returning run details for reporting randomness
- Use className instead of class when creating DOM elements
Pull Requests & Issues
-
Syntax highlighting in README.md
- Merges #973 from @brunoqc
-
Added a throw error block in describe incase a function with arguments is passed in describe
-
Remove unused
queueableFnarg fromonException- Fixes #958
-
Remove unused parameter from toThrowError
- Merges #957 from @FuzzySockets
-
Abort spying when the target cannot be spied upon
-
Removed GOALS_2.0.md, doesn’t seem to be needed anymore
- Merges #954 from @matthewhuff89
-
Change #xit so that it will output a more BDD-style pending message
-
Allow tests to run in random order
- Merges #927 from @marcioj
-
Use toString for objects if it has been overriden
-
Fix circles/x from getting cut off on Mac/chrome
- Merges #932 from @James-Dunn
-
Postpone find() until it is needed
-
check for global before assigning
-
Reverse suite afterEach behavior to match semantics?
- Merges #908 from @mcamac
-
Use badges from shields.io
- Merges #902 from @SimenB
-
xdescribe marks pending, plus associated tests.
-
Update glob to latest
-
Remove moot
versionproperty from bower.json- Merges #874 from @kkirsche
-
add toHaveBeenCalledTimes matcher
-
Update CONTRIBUTING.md
- Merges #856 from @lpww
-
Make the HtmlReport CSS classes “unique enough”
-
Raise an error when jasmine.any() isn’t passed a constructor
_Release Notes generated with Anchorman