[JAVA-2613] CustomMatchers#getFieldNames ignores superclass fields Created: 26/Sep/17 Updated: 29/Oct/23 Resolved: 16/Oct/17 |
|
| Status: | Closed |
| Project: | Java Driver |
| Component/s: | Test Coverage |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Jeffrey Yemin | Assignee: | Jeffrey Yemin |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
The bug in the matcher is due to a misunderstanding of how Groovy appends elements to a list: specifically, the += operator returns a new list rather than modifying the existing one. |
| Comments |
| Comment by Githook User [ 16/Oct/17 ] | |||||||||
|
Author: {'email': 'jeff.yemin@10gen.com', 'name': 'Jeff Yemin', 'username': 'jyemin'}Message:
Also fix one test bug that was exposed by this fix | |||||||||
| Comment by Jeffrey Yemin [ 26/Sep/17 ] | |||||||||
|
This will fix it:
When testing this fix, also found that static fields need to be excluded from the declared fields, and that DefaultServerConnectionSpecification tests are failing when comparing the commandListener property (not clear why). |