-
Notifications
You must be signed in to change notification settings - Fork 583
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
Update deprecated code to recommended strategy #6078
base: main
Are you sure you want to change the base?
Conversation
This is a continuation of the effort to update deprecated code Removed AvailablePortMatcherTests because it is a test of a testing component that is no longer needed Focused on replacing the rule ExpectedException.none() with AssertJ's exception testing facilities Signed-off-by: Glenn Renfro <[email protected]> cleanup Signed-off-by: Glenn Renfro <[email protected]>
@@ -51,6 +51,11 @@ | |||
<artifactId>spring-boot-starter-test</artifactId> | |||
<scope>test</scope> | |||
</dependency> | |||
<dependency> |
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.
Neither this, nor awaitility (above) is required as it piggybacks on spring-boot-starter-test.
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.
Ran a test so in this case awaitility is a required dependency.
@@ -51,6 +51,11 @@ | |||
<artifactId>spring-boot-starter-test</artifactId> | |||
<scope>test</scope> | |||
</dependency> | |||
<dependency> |
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.
Neither this, nor awaitility (above) is required as it piggybacks on spring-boot-starter-test.
import java.util.HashMap; | ||
import java.util.Map; | ||
import org.junit.Rule; | ||
|
||
import org.junit.Test; |
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.
Since you are in here already, do you mind replacing Junit4 test w/ Junit5 test?
|
||
@Rule | ||
public ExpectedException exception = ExpectedException.none(); | ||
public class AdditionalEnvironmentValidatorTests { | ||
|
||
@Test | ||
public void throw_exception_when_additional_environment_variables_contain_docker_variables() { |
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.
[UNRELATED] Oh my word, who named these tests. Is this python 🤣
exception.expectMessage("cannot exist in your additional environment"); | ||
AdditionalEnvironmentValidator.validate(variables); | ||
|
||
assertThatIllegalStateException().isThrownBy(() ->AdditionalEnvironmentValidator.validate(variables)). |
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.
Nice improvement @cppwfs - thanks.
@BeforeEach | ||
void init() { | ||
MockitoAnnotations.initMocks(this); | ||
autoCloseable = MockitoAnnotations.openMocks(this); |
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.
[UNRELATED] This was already here I know. The usage of @Mock
has turned out to be more hassle than its worth. Like in this case, its a single mock and we have this setup/teardown to deal w/.
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.
Nice improvements @cppwfs - thanks you.
Only suggestion is to rid all of these modified tests of the Junit 4 org.junit.Test
annotation.
Signed-off-by: Glenn Renfro <[email protected]>
This is a continuation of the effort to update deprecated code
Removed AvailablePortMatcherTests because it is a test of a testing component that is no longer needed
Focused on replacing the rule ExpectedException.none() with AssertJ's exception testing facilities