[SERVER-12919] jstest tool helpers do not check passthrough configuration Created: 26/Feb/14  Updated: 06/Dec/22  Resolved: 11/May/20

Status: Closed
Project: Core Server
Component/s: Testing Infrastructure
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Shaun Verch Assignee: Backlog - Server Tooling and Methods (STM) (Inactive)
Resolution: Won't Fix Votes: 0
Labels: stm, tig-mongorunner
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-11127 Add more tests for ssl client options Closed
Related
related to SERVER-6368 Make ToolTest run with auth when runn... Closed
Assigned Teams:
Server Tooling & Methods
Operating System: ALL
Participants:

 Description   

Some of the "passthrough tests" in our javascript testing framework work by setting some global configuration that gets checked by all the shell helpers that spawn new programs.

For example, running smoke.py with --use-ssl, will use the "--eval" in the mongo shell to set some global configuration that signals to all the shell helpers to spawn programs with ssl options.

You can see an example of a place where this configuration is checked here: https://github.com/mongodb/mongo/blob/r2.6.0-rc0/src/mongo/shell/servers.js#L421

However, the two helpers for spawning "tools" from the mongo shell for the purposes of jstests ignore this configuration, which means the tools to not benefit from the extra test coverage in the passthrough testing:
https://github.com/mongodb/mongo/blob/r2.6.0-rc0/src/mongo/shell/servers.js#L702
https://github.com/mongodb/mongo/blob/r2.6.0-rc0/src/mongo/shell/servers_misc.js#L58



 Comments   
Comment by Ryan Timmons [ 11/May/20 ]

Closing as wont-fix to indicate that there is currently no intention of doing this. Please re-open if there is priority for this. Perhaps this change could self-service by an appropriate server team if this is necessary rather than having to go thru the STM prioritization queue.

Generated at Thu Feb 08 03:30:03 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.