[SERVER-8229] Write more extensive unit tests of validateBSON() Created: 18/Jan/13 Updated: 26/Oct/21 Resolved: 26/Oct/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 5.0.0 |
| Type: | Task | Priority: | Minor - P4 |
| Reporter: | Andy Schwerin | Assignee: | Geert Bosch |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Participants: |
| Description |
|
The validateBSON tests need improvement, in that they do not actively attempt to circumvent the validator. There are no tests of objects that are valid if you overrun the buffer, but not otherwise, no specific tests of subobjects that claim to be too large, etc. There are also only a few targeted tests of validating/rejecting specific field types. |
| Comments |
| Comment by Geert Bosch [ 26/Oct/21 ] |
|
We now have extensive checks between the new implementation of validateBSON and the old one using the bson_validate_fuzzer. This covers comprehensive testing of both valid and invalid BSON. |
| Comment by Max Hirschhorn [ 26/May/18 ] |
|
Reassigning to the Platforms team to see how necessary this ticket is anymore. It doesn't seem particularly urgent given that it has been open since 2013. |