Run caching unit tests with all supported backends
Open
Nobody has claimed this yet.
Server
- Dominant language
- Shell
- Stars
- 16
- Forks
- 16
- Avg merge
- 11h 11m
- Merged PRs (30d)
- 1
Description
Currently we can not test different caching backends on jenkins, because all jobs running on the same server need to share the same config.
Therefor QA should run the tests with all available backends:
| Backend | Test | Result |
|---|---|---|
\OC\Memcache\APC |
./autotest.sh sqlite tests/lib/memcache/apc.php | ❔ |
\OC\Memcache\APCu |
./autotest.sh sqlite tests/lib/memcache/apcu.php | ❔ |
\OC\Memcache\Memcached |
./autotest.sh sqlite tests/lib/memcache/memcached.php | ❌ https://github.com/owncloud/core/pull/23218 |
\OC\Memcache\Redis |
./autotest.sh sqlite tests/lib/memcache/redis.php | ❔ |
\OC\Memcache\Xcache |
./autotest.sh sqlite tests/lib/memcache/xcache.php | ❔ |
Could also be automated with a docker for each caching backend?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with autotest.sh and the backend-specific tests under tests/lib/memcache/, including apc.php, apcu.php, memcached.php, redis.php, and xcache.php. Run or inspect the listed commands and determine how QA can exercise every backend despite shared Jenkins configuration; done means each backend has a reproducible test result or documented automation path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100