-
Notifications
You must be signed in to change notification settings - Fork 27.4k
it should be possible to created unimplemented specs #165
Comments
Bump! This feature is very useful in QUnit, since it allows a QA team and a dev team to agree on a common interface of test expectations at the start of a development cycle. Since unimplemented tests fail with a specific "Not Implemented" error, this allows build scripts to flag these tests as warnings--but not errors--allowing checkins to proceed. Developers can then "chip away" at these tests as they implement code. This feature also helps to make code coverage reports more meaningful. To improve code coverage, developers will sometimes "cheat" by adding just enough test code to make their production code run even though they haven't covered all needed cases. Then since the code coverage tool is happy, it's hard to figure out where the test gaps are. Having a feature like this allows dev teams to require a complete and meaningful "test skeleton" to be checked in first, showing all the test cases that eventually should be implemented (even if the developer doesn't have time to implement them all in one big bang). |
Would you like to provide a pull request? Does Jasmine have this in its latest release? |
@petebacondarwin : Yes, Jasmine has this in the master branch, which will eventually be released as 2.0: See: jasmine/jasmine#395 At the moment, I'm only dabbling in Angular (I'm mostly a Backbone dev) so I probably won't be able to create a PR anytime soon. Maybe there's a pattern that could be easily borrowed from Jasmine. |
we are slowly making our way to migrate over to Protractor which uses proper jasmine/mocha/whatever. If you really care about this feature, please submit a PR and reopen this issue. thanks! |
we should make it possible to specify specs before they are fully implemented.
I believe that jasmine (and for sure rspec) allows you do this just by creating an
it
without the spec body. like this:it('should do foo');
it('should do bar');
it('should do baz');
We should display the number of unimplemented specs in the overview.
The text was updated successfully, but these errors were encountered: