Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Work to reduce test time by reducing some repeated tests, using Awaitility, and reducing delays #3019

Merged
merged 2 commits into from
Jul 25, 2023

Conversation

dlvenable
Copy link
Member

Description

This PR includes some attempts to improve our test times.

  • Adds use of Awaitility instead of Thread.sleep in some locations.
  • Reduces repeated tests in AggregateProcessorIT, which is a particularly slow test.
  • Reduces some delays/timeouts.

Issues Resolved

N/A

Check List

  • New functionality includes testing.
  • New functionality has been documented.
    • New functionality has javadoc added
  • Commits are signed with a real name per the DCO

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

…ility, and reducing some wait times.

Signed-off-by: David Venable <[email protected]>
@@ -137,7 +137,7 @@ private AggregateProcessor createObjectUnderTest() {
return new AggregateProcessor(aggregateProcessorConfig, pluginMetrics, pluginFactory, expressionEvaluator);
}

@RepeatedTest(value = 10)
@RepeatedTest(value = 2)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't see an issue with just removing the @RepeatedTest annotation all together from these tests

Copy link
Collaborator

@asifsmohammed asifsmohammed left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just curious, how did you verify or analyze test times? Is it using build scan?

@dlvenable
Copy link
Member Author

Just curious, how did you verify or analyze test times? Is it using build scan?

I viewed the JUnit reports for these tests. That is also how I found some of the longer running tests.

@dlvenable dlvenable merged commit 68b420c into opensearch-project:main Jul 25, 2023
24 checks passed
@dlvenable dlvenable deleted the reduce-test-sleeps branch November 10, 2023 19:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants