antirez
d90e3e3a70
Sentinel test: add stub for unit 04.
2014-02-25 15:55:37 +01:00
antirez
89d95ec2e7
Sentinel test: added TODO items in 02 unit.
2014-02-25 15:55:37 +01:00
antirez
fe05112029
Sentinel test: check role at end of unit 01.
2014-02-25 15:08:41 +01:00
antirez
9e34e296cf
Sentinel test: kill masters instead of using DEBUG SLEEP in all tests.
2014-02-25 15:08:34 +01:00
antirez
dfacfafc2a
Sentinel test: restart instances left killed by previous unit.
...
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.
2014-02-25 10:30:35 +01:00
antirez
a6d560db64
Sentinel test: test majority crashing Sentinels.
...
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.
2014-02-25 10:30:35 +01:00
antirez
e8e2ac072c
Sentinel test: more stuff mored from 00-base to init.
...
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).
2014-02-25 10:30:35 +01:00
antirez
2d48d7c2fc
Sentinel test: removed useless code to set SDOWN timeout.
...
The new common initialization code used to start a new unit already set
the timeout to 2000 milliseconds.
2014-02-25 10:30:35 +01:00
antirez
d31a394148
Sentinel test: added empty units to fill later.
2014-02-25 10:30:35 +01:00
antirez
1dfab3d107
Sentinel test: framework improved and conf-update unit added.
...
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.
2014-02-25 10:30:35 +01:00
antirez
aee165e084
Sentinel test: move init tests as includes.
...
Most units will start with these two basic tests to create an
environment where the real tests are ran.
2014-02-25 10:30:35 +01:00
antirez
73b290cc5b
Sentinel test: ability to run just a subset of test files.
2014-02-25 10:30:35 +01:00
antirez
05dde71919
Sentinel test: some reliability fixes to 00-base tests.
2014-02-20 12:28:03 +01:00
antirez
c499d82f28
Sentinel test: check that role matches at end of 00-base.
2014-02-20 12:28:03 +01:00
antirez
c01aff1234
Sentinel test: ODOWN and agreement.
2014-02-20 12:28:03 +01:00
antirez
56cb037a86
Sentinel test: check reconfig of slaves and old master.
2014-02-20 12:28:03 +01:00
antirez
d4edf63bc4
Sentinel test: basic failover tested. Framework improvements.
2014-02-20 12:28:02 +01:00
antirez
722d4f0c41
Sentinel test: basic tests for MONITOR and auto-discovery.
2014-02-20 12:28:02 +01:00
antirez
b26660e130
Sentinel test: info fields, master-slave setup, fixes.
2014-02-20 12:28:02 +01:00
antirez
ac5fd5a519
Prefix test file names with numbers to force exec order.
2014-02-20 12:28:02 +01:00
antirez
890559ea1c
Sentinel test: provide basic commands to access instances.
2014-02-20 12:28:02 +01:00
antirez
351e790032
Sentinel: initial testing framework.
...
Nothing tested at all so far... Just the infrastructure spawning N
Sentinels and N Redis instances that the test will use again and again.
2014-02-17 17:38:58 +01:00
