[SERVER-31752] The geo_near_random helpers should assert that commands worked Created: 27/Oct/17 Updated: 06/Dec/22 Resolved: 28/Jun/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Kyle Suarez | Assignee: | Backlog - Query Team (Inactive) |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | query-44-grooming | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Query
|
||||
| Participants: | |||||
| Linked BF Score: | 0 | ||||
| Description |
|
We should also sweep through the helper functions in jstests/libs/geo_near_random.js. There are also commands in there that are run without asserting that they succeed, like building indexes. |
| Comments |
| Comment by David Storch [ 28/Jun/19 ] |
|
We are not planning to pursue this improvement at the moment. This would be good cleanup to address if we need to modify the geo_near_random helpers for any other reason, but we don't plan to schedule it independently. |
| Comment by Kaloian Manassiev [ 21/Mar/18 ] |
|
The sharded geo_near_random*.js tests have been cleaned up to assert that the sharding operations work like the original description of this ticked was asking for (this was done as part of unrelated work). I am repurposing the ticket to be about cleaning-up the geo_near test helpers in general and assigning to the query team. |