Oran Agra 87321deb3f attempt to fix tracking test issue with external tests due to lazy free (#9722) 3 éve
..
assets 3ca6972ecd Replace all usage of ziplist with listpack for t_zset (#9366) 3 éve
cluster 48d54265ce Fix failing cluster tests (#9707) 3 éve
helpers cf61ad14cc When redis-cli received ASK, it didn't handle it (#8930) 3 éve
integration 58a1d16ff6 Fix timing issue in replication test (#9719) 3 éve
modules f1f3cceb50 fix valgrind issues with long double module test (#9709) 3 éve
sentinel 53ad5627b7 Sentinel: Fix failed daily tests, due to race condition (#9501) 3 éve
support 87321deb3f attempt to fix tracking test issue with external tests due to lazy free (#9722) 3 éve
tmp ab72b4833d minor fixes to the new test suite, html doc updated 14 éve
unit 87321deb3f attempt to fix tracking test issue with external tests due to lazy free (#9722) 3 éve
README.md 6600253046 Client eviction ci issues (#9549) 3 éve
instances.tcl 48d54265ce Fix failing cluster tests (#9707) 3 éve
test_helper.tcl c1718f9d86 Replication backlog and replicas use one global shared replication buffer (#9166) 3 éve

README.md

Redis Test Suite

The normal execution mode of the test suite involves starting and manipulating local redis-server instances, inspecting process state, log files, etc.

The test suite also supports execution against an external server, which is enabled using the --host and --port parameters. When executing against an external server, tests tagged external:skip are skipped.

There are additional runtime options that can further adjust the test suite to match different external server configurations:

Option Impact
--singledb Only use database 0, don't assume others are supported.
--ignore-encoding Skip all checks for specific encoding.
--ignore-digest Skip key value digest validations.
--cluster-mode Run in strict Redis Cluster compatibility mode.

Tags

Tags are applied to tests to classify them according to the subsystem they test, but also to indicate compatibility with different run modes and required capabilities.

Tags can be applied in different context levels:

  • start_server context
  • tags context that bundles several tests together
  • A single test context.

The following compatibility and capability tags are currently used:

Tag Indicates
external:skip Not compatible with external servers.
cluster:skip Not compatible with --cluster-mode.
tls:skip Not campatible with --tls.
needs:repl Uses replication and needs to be able to SYNC from server.
needs:debug Uses the DEBUG command or other debugging focused commands (like OBJECT).
needs:pfdebug Uses the PFDEBUG command.
needs:config-maxmemory Uses CONFIG SET to manipulate memory limit, eviction policies, etc.
needs:config-resetstat Uses CONFIG RESETSTAT to reset statistics.
needs:reset Uses RESET to reset client connections.
needs:save Uses SAVE to create an RDB file.

When using an external server (--host and --port), filtering using the external:skip tags is done automatically.

When using --cluster-mode, filtering using the cluster:skip tag is done automatically.

In addition, it is possible to specify additional configuration. For example, to run tests on a server that does not permit SYNC use:

./runtest --host <host> --port <port> --tags -needs:repl