This test is unnecessary

FagnerMartinsBrack · FagnerMartinsBrack · commit 50b0b088d3b5 · 2015-03-23T23:00:22.000-03:00
It was initially created to confirm "removeCookie" was returning "false"
in the case it couldn't be able to remove the cookie. But the only thing
it is doing is to stub the API and force returning false, there is no
real value on this test.

If you change the boolean return of "removeCookie", 2 tests fail anyway,
"removeCookie: when cookie does not exist" and "removeCookie: when
sucessfully deleted". All evidences points out this test is really
unnecessary and non-deterministic.

Also, this test relies in internal behavior for stubbing, future code
changes might require the modification of an unrelated test, which is
not ideal.
diff --git a/test/tests.js b/test/tests.js
@@ -288,26 +288,6 @@ test('when cookie does not exist', function () {
 	strictEqual(Cookies.remove('c'), true, 'returns true');
 });
 
-// The following test relies on internals, any change here might not be deterministic in the future.
-// Rewrite it later.
-
-//test('when deletion failed', function () {
-//	expect(1);
-//	$.cookie('c', 'v');
-//
-//	var originalCookie = $.cookie;
-//	$.cookie = function () {
-//		// Stub deletion...
-//		if (arguments.length === 1) {
-//			return originalCookie.apply(null, arguments);
-//		}
-//	};
-//
-//	strictEqual($.removeCookie('c'), false, 'returns false');
-//
-//	$.cookie = originalCookie;
-//});
-
 test('with options', function () {
 	expect(1);
 	var options = { path: '/' };
