Proposal: Mark jedis test cases based on compatible redis versions

[cjx-zar]

This is a very nice project! And I would like to propose an improvement for the existing jedis testing framework. Recently, I have been working on redis testing frameworks and have noticed that the current jedis testing only targets the latest unstable branch of redis. However, this can make it difficult for projects that are based on stable versions of redis to pass the tests when using jedis to test their quality, even though their products are already well.

To address this issue, I suggest that all the test cases in jedis be marked based on the compatible redis versions. This will enable developers working on stable redis versions to test their products using jedis, providing an inclusive and comprehensive testing framework suitable for all developers.

I am enthusiastic about contributing to this effort and making jedis even better. I would appreciate your feedback on this proposal and look forward to hearing your thoughts.

Thank you for your attention.

[github-actions]

This issue is marked stale. It will be closed in 30 days if it is not updated.

[ggivo]

@cjx-zar

First of all sorry for the delayed feedback.

With PR - Introduces test matrix based on Redis versions [8.0-M1, 7.4.1, 7.2.6, 6.2.16] we have introduced a test matrix based on Redis server versions. This PR also introduces JUnit Rules to support annotating tests with the minimum required Redis server version or required command. It is more or less similar to your proposal A demo of redis version tag proposal #3473

• EnabledOnCommand - Tests annotated with EnabledOnCommand will be skipped if provided test Redis server does not support the command
• SinceRedisVersion. - Tests annotated with SinceRedisVersion will be skipped when executed against Redis server with a version that does not match the requested one.

Interested if this will suit your use case.
In case this issue is still relevant to you would appreciate your feedback.

Note : With PR - Migrate test to JUnit5 we are also in process of migrating JUnit4 rules to JUnit5 Conditions

[github-actions]

This issue is marked stale. It will be closed in 30 days if it is not updated.