[DRIVERS-2325] Add commandStartedEvent assertions to clustered index spec tests Created: 11/May/22 Updated: 20/May/22 |
|
| Status: | Implementing |
| Project: | Drivers |
| Component/s: | Collection Management |
| Fix Version/s: | None |
| Type: | Task | Priority: | Unknown |
| Reporter: | Jeremy Mikola | Assignee: | Jeremy Mikola |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | yaml-test | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Driver Changes: | Needed | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Downstream Changes Summary: | Drivers should sync collection-management unified spec tests to 600b1af. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Driver Compliance: |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Description |
Summaryb042e47 introduced spec tests where clusteredIndex is specified as an option for the create command helper (e.g. Database.createCollection). These tests do not actually assert that the option is passed to the server. In particular, the "createCollection with clusteredIndex" test only asserts that the newly created collection exists after the createCollection operation is executed. Thankfully, the "listCollections includes clusteredIndex" and "listIndexes returns the index" should be suitable guarantee driver correctness, since those tests will fail if clusteredIndex is not correctly passed to create. MotivationIs this issue urgent?No. Is this ticket required by a downstream team?No. Is this ticket only for tests?Yes. |
| Comments |
| Comment by Githook User [ 17/May/22 ] |
|
Author: {'name': 'Jeremy Mikola', 'email': 'jmikola@gmail.com', 'username': 'jmikola'}Message: DRIVERS-2325: commandStartedEvent assertions for clusteredIndex tests (#1217) |
| Comment by Jeremy Mikola [ 16/May/22 ] |