diff options
| author | Paul J. Davis <paul.joseph.davis@gmail.com> | 2017-02-02 11:23:16 -0600 |
|---|---|---|
| committer | Paul J. Davis <paul.joseph.davis@gmail.com> | 2017-04-18 14:07:24 -0500 |
| commit | c0fda54d3ed4f06f1e41db598859de23aaf0e3ac (patch) | |
| tree | e123d08b2f6af7e58e084ad9a990aea0fd90565d | |
| parent | a9dd4c4cc86634e4bd9c0ec7d947c12e467d1c7f (diff) | |
| download | couchdb-c0fda54d3ed4f06f1e41db598859de23aaf0e3ac.tar.gz | |
Fix mem3_sync_event_listener unit test
The `should_restart_listener` test was failing because the pattern
supplied to meck was wrong. The argument to
`config_notifier:handle_event/2` is of the pattern `{config_change,
Section, Key, Value, Persist}` but the test was only matching a
four-tuple which I assume was missing the `config_change` atom in the
argument.
COUCHDB-3380
| -rw-r--r-- | src/mem3/src/mem3_sync_event_listener.erl | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/mem3/src/mem3_sync_event_listener.erl b/src/mem3/src/mem3_sync_event_listener.erl index 7859c3109..cd671e4d5 100644 --- a/src/mem3/src/mem3_sync_event_listener.erl +++ b/src/mem3/src/mem3_sync_event_listener.erl @@ -223,7 +223,7 @@ setup() -> ok = meck:new(config_notifier, [passthrough]), ok = meck:expect(config_notifier, handle_event, [ - {[{'_', '_', "error", '_'}, '_'], meck:raise(throw, raised_error)}, + {[{'_', '_', '_', "error", '_'}, '_'], meck:raise(throw, raised_error)}, {['_', '_'], meck:passthrough()} ]), |