- 06 Sep, 2020 3 commits
-
-
Oran Agra authored
in some cases a command that returns an error possibly due to a timing issue causes the tcl code to crash and thus prevents the rest of the tests from running. this adds an option to make the test proceed despite the crash. maybe it should be the default mode some day.
-
Oran Agra authored
- skip full units - skip a single test (not just a list of tests) - when skipping tag, skip spinning up servers, not just the tests - skip tags when running against an external server too - allow using multiple tags (split them)
-
Oran Agra authored
-
- 13 Jul, 2020 1 commit
-
-
Oran Agra authored
in the majority of the cases (on this rarely used feature) we want to stop and be able to connect to the shard with redis-cli. since these are two different processes interracting with the tty we need to stop both, and we'll have to hit enter twice, but it's not that bad considering it is rarely used.
-
- 29 Oct, 2019 1 commit
-
-
Oran Agra authored
sometimes we have several assertions with the same condition in the same test at different stages, and when these fail (the ones that print the condition text) you don't know which one it was. other assertions didn't print the condition text (variable names), just the expected and unexpected values. So now, all assertions print context line, and conditin text. besides, one of the major differences between 'assert' and 'assert_equal', is that the later is able to print the value that doesn't match the expected. if there is a rare non-reproducible failure, it is helpful to know what was the value the test encountered and how far it was from the threshold. So now, adding assert_lessthan and assert_range that can be used in some places. were we used just 'assert { a > b }' so far.
-
- 30 Sep, 2019 1 commit
-
-
Madelyn Olson authored
-
- 30 Jul, 2018 1 commit
-
-
Oran Agra authored
* allowing --single to be repeated * adding --only so that only a specific test inside a unit can be run * adding --skiptill useful to resume a test that crashed passed the problematic unit. useful together with --clients 1 * adding --skipfile to use a file containing list of tests names to skip * printing the names of the tests that are skiped by skipfile or denytags * adding --config to add config file options from command line
-
- 25 Apr, 2016 1 commit
-
-
Oran Agra authored
-
- 02 Jan, 2015 1 commit
-
-
Matt Stancliff authored
This replaces individual ziplist vs. linkedlist representations for Redis list operations. Big thanks for all the reviews and feedback from everybody in https://github.com/antirez/redis/pull/2143
-
- 29 Sep, 2014 1 commit
-
-
Matt Stancliff authored
-
- 22 Feb, 2014 1 commit
-
-
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.
-
- 17 Feb, 2014 1 commit
-
-
antirez authored
-
- 26 Apr, 2012 2 commits
-
-
antirez authored
Now it uses the new wait_for_condition testing primitive. Also wait_for_condition implementation was fixed in this commit to properly escape the expr command and its argument.
-
antirez authored
A new primitive wait_for_condition was introduced in the scripting engine that makes waiting for events simpler, so that it is simpler to write tests that are more resistant to timing issues.
-
- 06 Jan, 2012 1 commit
-
-
antirez authored
Regression test for the main problem causing issue #141. Minor changes/fixes/additions to the test suite itself needed to write the test.
-
- 21 Dec, 2011 1 commit
-
-
antirez authored
Redis test: when assertion fails print not just the expression but also expanded values in the error message.
-
- 28 Jul, 2011 1 commit
-
-
antirez authored
-
- 11 Jul, 2011 1 commit
-
-
antirez authored
-
- 10 Jul, 2011 3 commits
- 25 Jun, 2011 1 commit
-
-
antirez authored
-
- 22 Feb, 2011 1 commit
-
-
antirez authored
fixed color support for test suite. Now colors are shown as long as there is xterm somewhere inside the TERM env var
-
- 15 Dec, 2010 3 commits
- 10 Dec, 2010 1 commit
-
-
Pieter Noordhuis authored
-
- 15 Oct, 2010 1 commit
-
-
Pieter Noordhuis authored
-
- 01 Aug, 2010 1 commit
-
-
Pieter Noordhuis authored
-
- 29 Jul, 2010 1 commit
-
-
Pieter Noordhuis authored
-
- 16 Jun, 2010 1 commit
-
-
Pieter Noordhuis authored
-
- 15 Jun, 2010 1 commit
-
-
Pieter Noordhuis authored
-
- 14 Jun, 2010 1 commit
-
-
Pieter Noordhuis authored
-
- 04 Jun, 2010 1 commit
-
-
Pieter Noordhuis authored
-
- 02 Jun, 2010 4 commits
-
-
Pieter Noordhuis authored
-
Pieter Noordhuis authored
-
Pieter Noordhuis authored
-
Pieter Noordhuis authored
-
- 25 May, 2010 1 commit
-
-
antirez authored
-
- 15 May, 2010 1 commit
-
-
Pieter Noordhuis authored
print warnings in redis log when a test raises an exception (very likely to be caused by something like a failed assertion)
-