Sheel Choksi f7ff47706c Remove 'empty' as an option as a spec result ...

- Having the 'empty' state for a spec result can be considered a
breaking change to the reporter interface
- Instead, we determine if a spec has no expectations using the added
key of 'passedExpectations' in combination of the 'failedExpectations'
to determine that there a spec is 'empty'

[fixes #73741032]

2014-06-27 23:50:28 -07:00

..

boot

- Add a main entry point for the jasmine-core npm

2014-03-21 17:21:52 -07:00

example

- Add a main entry point for the jasmine-core npm

2014-03-21 17:21:52 -07:00

__init__.py

Create jasmine-core python egg

2014-03-11 13:40:28 -07:00

boot.js

Bump built distribution copyright's for 2014

2014-01-04 23:11:20 -08:00

core.py

Create jasmine-core python egg

2014-03-11 13:40:28 -07:00

jasmine-html.js

Remove 'empty' as an option as a spec result

2014-06-27 23:50:28 -07:00

jasmine.css

namespace html-reporter -> jasmine_html-reporter

2014-06-22 21:47:46 -07:00

jasmine.js

Remove 'empty' as an option as a spec result

2014-06-27 23:50:28 -07:00

json2.js

Gem-ize jasmine

2011-06-17 21:01:42 -04:00

node_boot.js

- Add a main entry point for the jasmine-core npm

2014-03-21 17:21:52 -07:00

spec

Give Jasmine::Core access to jasmine specs

2011-06-18 09:39:23 -04:00

version.rb

Create a 2.0 distribution

2013-12-16 12:33:34 -08:00