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]
This commit is contained in:
@@ -194,10 +194,9 @@ describe("Spec", function() {
|
||||
expect(done).toHaveBeenCalled();
|
||||
});
|
||||
|
||||
it("#status returns empty by default", function(){
|
||||
var emptySpec = new j$.Spec({ fn: function () {} });
|
||||
emptySpec.execute();
|
||||
expect(emptySpec.status()).toBe("empty");
|
||||
it("#status returns passing by default", function(){
|
||||
var spec = new j$.Spec({ fn: function () {} });
|
||||
expect(spec.status()).toBe("passed");
|
||||
});
|
||||
|
||||
it("#status returns passed if all expectations in the spec have passed", function() {
|
||||
|
||||
Reference in New Issue
Block a user