-
Notifications
You must be signed in to change notification settings - Fork 1k
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
[UNDERTOW-2371] initialize the DefaultServer once to speed up test HttpContinueSslServletTestCase #1574
base: main
Are you sure you want to change the base?
Conversation
@TestBoost Could you please create a ticket? |
Sure, I just submit a ticket here https://issues.redhat.com/browse/UNDERTOW-2371. I don't know why the test class |
@TestBoost could you please force push again to trigger CI? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If marked method is not used, it should be removed?
} | ||
|
||
@Before | ||
public void before() throws Exception { | ||
public static void before() throws Exception { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this method even used now?
…tpContinueSslServletTestCase Signed-off-by: Flavia Rainone <[email protected]>
There are five tests in the test class
HttpContinueSslServletTestCase
. However, they reply on the same DefaultServer to send post http request. The time cost of start or stop for the DefaultServer is high. They are not modifying the contents of the DefaultServer, thus we can just initialize the DefaultServer once before or after all test methods inside test classHttpContinueSslServletTestCase
.The test runtime can jump from
5.43160 s
to1.8027 s
after applying these changes when run on our machine.