[JCBC-115] thoroughly test on_error arguments Created: 18/Sep/12 Updated: 20/May/13 |
|
| Status: | Open |
| Project: | Couchbase Java Client |
| Component/s: | library |
| Affects Version/s: | None |
| Fix Version/s: | 1.1.7 |
| Security Level: | Public |
| Type: | Improvement | Priority: | Major |
| Reporter: | Matt Ingenthron | Assignee: | Michael Nitschinger |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
Support for on_error was recently added, but it does does not currently have a test for on_error=stop.
|
| Comments |
| Comment by Michael Nitschinger [ 09/Nov/12 ] |
|
Mark,
Can you add this to your sdkd testsuite? Its hard to deal with this in unit tests (would require lots of mocking) and I assume you can shutdown nodes and verify the behavior is correct? Thanks, Michael |
| Comment by Michael Nitschinger [ 29/Nov/12 ] |
| We can do this in functional tests as well, there are easy ways to produce errors on the server. |
| Comment by Mark Nunberg [ 29/Nov/12 ] |
| Please share :) |