- 29 Sep, 2014 1 commit
-
-
Matt Stancliff authored
-
- 30 Jun, 2014 1 commit
-
-
antirez authored
-
- 18 Jun, 2014 1 commit
-
-
antirez authored
-
- 10 Jun, 2014 1 commit
-
-
antirez authored
-
- 19 May, 2014 1 commit
-
-
antirez authored
-
- 29 Apr, 2014 1 commit
-
-
antirez authored
-
- 24 Apr, 2014 2 commits
- 18 Mar, 2014 2 commits
- 04 Mar, 2014 4 commits
- 03 Mar, 2014 1 commit
-
-
antirez authored
-
- 25 Feb, 2014 2 commits
-
-
antirez authored
Sentinel tests are designed to be dependent on the previous tests in the same unit, so usually we can't continue with the next test in the same unit if a previous test failed.
-
antirez authored
Also kill_instance was modified to warn when a test will try to kill the same instance multiple times for error.
-
- 23 Feb, 2014 2 commits
- 22 Feb, 2014 1 commit
-
-
antirez authored
It is now possible to kill and restart sentinel or redis instances for more real-world testing. The 01 unit tests the capability of Sentinel to update the configuration of Sentinels rejoining the cluster, however the test is pretty trivial and more tests should be added.
-
- 20 Feb, 2014 2 commits
- 18 Feb, 2014 3 commits
- 17 Feb, 2014 1 commit
-
-
antirez authored
Nothing tested at all so far... Just the infrastructure spawning N Sentinels and N Redis instances that the test will use again and again.
-