antirez
da7d4088c5
Sentinel test: add stub for unit 04.
2014-02-25 15:36:51 +01:00
antirez
eb282315ff
Sentinel test: added TODO items in 02 unit.
2014-02-25 15:21:53 +01:00
antirez
808c9c16a9
Sentinel test: check role at end of unit 01.
2014-02-25 14:59:36 +01:00
antirez
ed309a8162
Sentinel test: kill masters instead of using DEBUG SLEEP in all tests.
2014-02-25 14:33:44 +01:00
antirez
9edf4e7c92
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 08:48:46 +01:00
antirez
0c63971394
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 08:29:12 +01:00
antirez
cd219998da
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-24 17:21:50 +01:00
antirez
c13ccbd3e5
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-24 16:57:52 +01:00
antirez
d97b0090a9
Sentinel test: added empty units to fill later.
2014-02-23 17:50:59 +01:00
antirez
6f02cfaeac
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-22 17:27:49 +01:00
antirez
8def3a143e
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-20 16:58:23 +01:00
antirez
8c378427b2
Sentinel test: ability to run just a subset of test files.
2014-02-20 16:28:41 +01:00
antirez
0cf419af0f
Sentinel test: some reliability fixes to 00-base tests.
2014-02-19 10:26:23 +01:00
antirez
6f298002de
Sentinel test: check that role matches at end of 00-base.
2014-02-19 10:08:49 +01:00
antirez
693385e2dc
Sentinel test: ODOWN and agreement.
2014-02-19 09:44:38 +01:00
antirez
4a22c51c48
Sentinel test: check reconfig of slaves and old master.
2014-02-18 17:03:56 +01:00
antirez
213cc0fe88
Sentinel test: basic failover tested. Framework improvements.
2014-02-18 16:31:52 +01:00
antirez
251d4f754d
Sentinel test: basic tests for MONITOR and auto-discovery.
2014-02-18 11:53:54 +01:00
antirez
bbd8a80fd4
Sentinel test: info fields, master-slave setup, fixes.
2014-02-18 11:38:49 +01:00
antirez
ad1e66fe4e
Prefix test file names with numbers to force exec order.
2014-02-18 11:07:42 +01:00
antirez
1310d19402
Sentinel test: provide basic commands to access instances.
2014-02-18 11:04:55 +01:00
antirez
576e405634
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:04 +01:00
