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
This commit is contained in:
Gregg Van Hove and Tim Jarratt
2013-10-01 16:28:33 -07:00
parent 70fb0f0ed5
commit cb8ba74937
3 changed files with 5 additions and 5 deletions

View File

@@ -451,7 +451,7 @@ getJasmineRequireObj().Env = function(j$) {
};
var getSpecName = function(spec, currentSuite) {
return currentSuite.getFullName() + ' ' + spec.description + '.';
return currentSuite.getFullName() + ' ' + spec.description;
};
// TODO: we may just be able to pass in the fn instead of wrapping here

View File

@@ -485,9 +485,9 @@ describe("Env integration", function() {
});
});
expect(topLevelSpec.getFullName()).toBe("my tests are sometimes top level.");
expect(nestedSpec.getFullName()).toBe("my tests are sometimes singly nested.");
expect(doublyNestedSpec.getFullName()).toBe("my tests are sometimes even doubly nested.");
expect(topLevelSpec.getFullName()).toBe("my tests are sometimes top level");
expect(nestedSpec.getFullName()).toBe("my tests are sometimes singly nested");
expect(doublyNestedSpec.getFullName()).toBe("my tests are sometimes even doubly nested");
});
it("Custom equality testers should be per spec", function(done) {

View File

@@ -81,7 +81,7 @@ getJasmineRequireObj().Env = function(j$) {
};
var getSpecName = function(spec, currentSuite) {
return currentSuite.getFullName() + ' ' + spec.description + '.';
return currentSuite.getFullName() + ' ' + spec.description;
};
// TODO: we may just be able to pass in the fn instead of wrapping here