[GODRIVER-2430] Drop and create collections consistently across runners Created: 19/May/22 Updated: 28/Nov/22 |
|
| Status: | Backlog |
| Project: | Go Driver |
| Component/s: | Testing |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Trivial - P5 |
| Reporter: | Benji Rewis (Inactive) | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
mtest.CreateCollection will create a collection and only drop it after the test has finished running. The new unified spec test runner will drop the collection at the beginning of the test before creating it. This means that running a unified spec test before running a test that uses mtest.CreateCollection can potentially leave collections undropped between tests. Since the unified test format spec explicitly says to drop the specified collection and then create it, we should probably change mtest.CreateCollection to either do the same or drop the collection before and after test execution. |
| Comments |
| Comment by Benji Rewis (Inactive) [ 19/May/22 ] |
|
See this PR comment for potential consequences of current behavior: https://github.com/mongodb/mongo-go-driver/pull/950#discussion_r877513442. |