[SERVER-58019] Write Integration Test with Release Tools Created: 23/Jun/21 Updated: 04/Dec/23 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Robert Guo (Inactive) | Assignee: | Backlog - Server Release Team |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Assigned Teams: |
Server Release
|
||||||||||||
| Backport Requested: |
v5.2, v5.1
|
||||||||||||
| Participants: | |||||||||||||
| Description |
|
1. Write an integration test that runs mongo-release-tools on the current version of evergreen.yml and assert that the output YAML is valid by running the YAML linters. (Note: we'll need to specify the specific things to enable for the linter to successfully pass.) 2. Add a small set of Python unittests and use PyYAML to check for specific values in the generated YAML. Document this part well so it can be made self-service in the future. May be easier for this to be in the mongo-release-tools repo. Make mongo-release-tools repo a module. 3. Run a compile task (on a new build variant) in the generated YAML and run it through generate.tasks; ensure the task can run successfully. |