Add option to disable caching

[ProLoser]

It's driving me knucking futs when I'm developing because if I run a test, it fails, then I re-run a test and it runs only the failed test and passes, but the third time with all tests it just fails again.

I would like to be able to pass an option to force testacular to ignore any cached results. It's also very frustrating when travis only runs 1 test instead of the entire suite (which seems to happen quite a bit for AngularUI and related PRs).

I have no idea why it passes if it runs just the 1 test vs all tests, and I even isolated that test manually by doing iit() but it still fails, so I don't think it's a problem with isolation cleanup.

[ProLoser]

An example of travis only running one test: https://travis-ci.org/douglasduteil/angular-ui/builds/4686364

Also, if you try running this AngularUI PR angular-ui/angular-ui-OLDREPO#412 twice in a row you will see it alternate between failing (all tests run) and passing (just the failed test runs). I've even had cases where it goes from all tests -> 6 tests -> 3 tests -> all tests and it makes me want to pull my hair out when I don't notice it.

[ProLoser]

Actually, the only time I might appreciate running just the failed tests is when I'm watching, not doing a run-once, but I'd still like to forcibly override this because I think there are some bugs with the caching system.

[vojtajina]

I think we are just gonna remove this feature "run only last failed tests". It's only jasmine feature and it's flaky anyway (as it relies on jasmine's ids which are based on order of registering tests, so it can actually happen, that the last failed test has a different id in next run, especially before fixing d759e40, and therefore it passes, because a different test is actually run).

However, I'm puzzled with the Travis. I have no idea why Travis is executing just one test. This "last failed tests" feature is definitely not causing it, as this is the first run, so there's no last failed tests. Are you sure you don't have iit in your tests ?

Btw, can you update to use to the latest Testacular ?

[vojtajina]

Added issue for it https://github.com/testacular/testacular-jasmine/issues/1

[ProLoser]

Updated. I'll have to do further testing and keep you guys informed re Travis.

[vojtajina]

Any updates on this ? I'm closing it as there's nothing like caching results in Testacular. I hope the only issue was because "run only last failed" anti-feature in jasmine adapter. I think we gonna remove it, see https://github.com/testacular/testacular/issues/148 for more info.

If you think there is some other issue than this "jasmine adapter feature", please re-open this issue.

[ProLoser]

Gotcha, I am sure that's it.
On Feb 20, 2013 7:56 PM, "Vojta Jina" notifications@github.com wrote:

Any updates on this ? I'm closing it as there's nothing like caching
results in Testacular. I hope the only issue was because "run only last
failed" anti-feature in jasmine adapter. I think we gonna remove it, see
#148 https://github.com/testacular/testacular/issues/148 for more info.

If you think there is some other issue than this "jasmine adapter
feature", please re-open this issue.

—
Reply to this email directly or view it on GitHubhttps://github.com/testacular/testacular/issues/344#issuecomment-13871784.