[JAVA-4342] Make ConnectivityTest faster and more informative Created: 11/Oct/21  Updated: 28/Oct/23  Resolved: 11/Oct/21

Status: Closed
Project: Java Driver
Component/s: Test Coverage
Affects Version/s: None
Fix Version/s: 4.4.0

Type: Improvement Priority: Unknown
Reporter: Jeffrey Yemin Assignee: Jeffrey Yemin
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to JAVA-4341 Evergreen: Atlas connectivity test fa... Closed

 Description   

When one of the Atlas connectivity tests is failing, it's slow and annoying to figure out which of the Atlas test connection strings is actually failing. This is because:

  1. We run the same test once for each URI, and the test results files just overwrite each other
  2. In order to make sure that all the tests run, we have to use --rerun-tasks, which makes the tests slow

We can fix both these problems by:

  1. Pass all the Atlas connection strings in to a single run of each ConnectivityTest, perhaps as a delimited list in a new system property, and
  2. Refactor each ConnectivityTest to be parameterized, and include the connection string (without credentials) as part of the test name, so that they are unique.


 Comments   
Comment by Githook User [ 11/Oct/21 ]

Author:

{'name': 'Jeff Yemin', 'email': 'jeff.yemin@mongodb.com', 'username': 'jyemin'}

Message: Fix Atlas connectivity tests (#798)

  • Ensure that they all run
  • Ensure that all results are reported
  • Speed them up by running all in a single Gradle invocation

JAVA-4342
Branch: master
https://github.com/mongodb/mongo-java-driver/commit/e9c2fe4cee325d6fbd3c4feb72a02619ead36bf2

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