[SERVER-61109] Have resmoke support multiple config directories Created: 29/Oct/21 Updated: 27/Oct/23 Resolved: 05/Apr/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Jason Chan | Assignee: | Backlog - Replication Team |
| Resolution: | Works as Designed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Replication
|
||||
| Participants: | |||||
| Story Points: | 1 | ||||
| Description |
|
We have non-server projects (like mongosync) that check out resmoke and leverage existing server tests to generate workloads as part of testing. It would be nice if resmoke could track suites across multiple config directories. AC:
|
| Comments |
| Comment by Vishnu Kaushik [ 04/Apr/22 ] |
|
I guess there isn't any action to be performed in this ticket then, since the only work specified here is to pick up tests from the correct spot in the YAML, as Jason showed above. |
| Comment by Jason Chan [ 18/Feb/22 ] |
|
Re-opening since this is something we probably want to avoid having c2c-specific tests live in the server project. Assigning to Replication for now. |
| Comment by Robert Guo (Inactive) [ 10/Dec/21 ] |
|
We weren't able to slot this into the project unfortunately but it's not a huge change. The CONFIG_DIR option needs to be changed to a list. It is only used to generate named suites and there is one test so it should be a straightforward fix. |