[JAVA-4502] Use a separate task for each AWS test scenario Created: 16/Feb/22 Updated: 28/Oct/23 Resolved: 17/Feb/22 |
|
| Status: | Closed |
| Project: | Java Driver |
| Component/s: | Test Improvement |
| Affects Version/s: | None |
| Fix Version/s: | 4.6.0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Jeffrey Yemin | Assignee: | Jeffrey Yemin |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | QP-priority | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Epic Link: | CSFLE AWS on-demand credentials |
| Quarter: | FY23Q1 |
| Documentation Changes: | Not Needed |
| Description |
|
Currently all the scenarios are tested in a single task, with a function defined for each one. That is problematic because each function runs the Gradle build, and the test names overlap. So that means that it's difficult to see failures if just one of the scenarios fails. The Evergreen config should be updated so that each scenario runs in its own task. |
| Comments |
| Comment by Githook User [ 17/Feb/22 ] |
|
Author: {'name': 'Jeff Yemin', 'email': 'jeff.yemin@mongodb.com', 'username': 'jyemin'}Message: Use a separate Evergreen task for each AWS test scenario (#880)
|