Details
-
Task
-
Resolution: Fixed
-
Major
-
.master
-
None
Description
The memcached_testapp unit tests currently only run against the default (aka memcache) bucket type.
While these tests are primarily designed to test the memcached front-end, there is value in also running them against ep_engine given that's the more common engine.
(Note: we otherwise don't have any tests which run memcached + final ep.so binaries together - the ep_engine black-box tests (testing final ep.so shared library) use engine_testapp which isn't quite the same as memcached.
Attachments
Issue Links
- is duplicated by
-
MB-17953 Extend memcache tests to be able to select between default and ep engines.
- Closed
For Gerrit Dashboard: MB-19606 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
66409,3 | MB-19606 Hacky code to run memcached_testapp against ep.so | master | memcached | Status: ABANDONED | 0 | -1 |
72884,6 | MB-19606: Allow test execution against ep-engine | master | memcached | Status: MERGED | +2 | +1 |
78141,3 | MB-19606: Use GET_AND_LOCK to lock items; allow 0 length stats. | master | memcached | Status: MERGED | +2 | +1 |
78321,4 | MB-19606: Add test for running memcached_testapp against ep_engine | master | ep-engine | Status: ABANDONED | 0 | -1 |
78839,4 | MB-19606: Add test for running memcached_testapp against ep_engine | master | kv_engine | Status: ABANDONED | 0 | -1 |