- 05 Mar, 2014 1 commit
-
-
antirez authored
-
- 25 Feb, 2014 12 commits
-
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
An unit can abort in the middle for an error. The next unit should not assume that the instances are in a clean state, and must restart what was left killed.
-
antirez authored
The test was previously performed by removing the master from the Sentinel monitored masters. The test with the Sentinels crashed is more similar to real-world partitions / failures.
-
antirez authored
The area a number of mandatory tests to craete a stable setup for testing that is not too sensitive to timing issues. All those tests moved to includes/init-tests, and marked as (init).
-
antirez authored
The new common initialization code used to start a new unit already set the timeout to 2000 milliseconds.
-
antirez authored
-
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.
-
antirez authored
Most units will start with these two basic tests to create an environment where the real tests are ran.
-
antirez authored
-
- 20 Feb, 2014 9 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.
-