antirez
edf48d17a2
Sentinel test: jump to next unit on test failure.
...
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.
2014-02-25 10:24:16 +01:00
antirez
491bcbaf73
Sentinel test: restart_instance should refresh pid attrib.
...
Also kill_instance was modified to warn when a test will try to kill the
same instance multiple times for error.
2014-02-25 10:24:16 +01:00
antirez
b18109e351
Sentinel test: minor fixes to --pause-on-error.
2014-02-25 10:24:16 +01:00
antirez
2ed707bcaa
Sentinel test: --pause-on-error option added.
...
Pause the test with running instances available for state inspection on
error.
2014-02-25 10:24:16 +01:00
antirez
ec593b582e
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:24:16 +01:00
antirez
ef01bbe1f5
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:24:16 +01:00
antirez
2b4bc4f900
Sentinel test: ability to run just a subset of test files.
2014-02-25 10:24:16 +01:00
antirez
f7cb83778b
Sentinel test: basic failover tested. Framework improvements.
2014-02-20 12:28:18 +01:00
antirez
8292dd50cd
Sentinel test: info fields, master-slave setup, fixes.
2014-02-20 12:28:18 +01:00
antirez
bbbe68aa0d
Sentinel test: provide basic commands to access instances.
2014-02-20 12:28:18 +01:00
antirez
2a35abcf12
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:39:23 +01:00
