[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)

JAVA-4502
Branch: master
https://github.com/mongodb/mongo-java-driver/commit/8c68972b6b5278bc42b702b6837236b2c6fedbc2

Generated at Thu Feb 08 09:02:15 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.