-
Notifications
You must be signed in to change notification settings - Fork 4
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
Change annotation name #43
Conversation
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.
I was hoping to some aggressive discussion/voting on that issue. I have to say my favorite is @ContainerRuntimeRequired
.
And we can have that. :) I just pushed this so I didn't lose the changes I had locally. |
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.
After more discussions with @jamezp I believe this should be actually called '@TestcontainersRequired'. What we need the annotation to specify, is that Testcontainers client works. This is to my knowledge currently the same as podman or docker required, but this may not always be the case. Also, that's what the implementation checks for.
This makes the most sense to me as well. |
* | ||
* <pre> | ||
* @ExtendWith(ArquillianExtension.class) | ||
* @RunAsClient | ||
* // By throwing the TestAbortedException, the test will be skipped if docker is not available | ||
* // By throwing the TestAbortedException, the test will be skipped if a container engine is not available |
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.
This is a very minor comment. Should this "a Testcontainer engine"? I don't have a real strong opinion either way.
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.
I also think this needs a different wording, but I am not yet sure what's the ideal wording :)
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.
I'm fine to leave it as is, but no strong opinion either. I think, though, that the "engine" is either Docker or Podman (at this point), whereas Testcontainers is the... orchestration tool that starts a "container" using whatever "engine" is available in the environment.
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.
I also think this needs a different wording, but I am not yet sure what's the ideal wording :)
Well, it seems that whole Javadoc is pretty outdated anyway. That sample code is pretty rough. Let me revisit that...
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.
Though "Testcontainer engine" is not a thing, how about going the descriptive way something like "the test will be skipped if Testcontainers requirements are not available." or just "Testcontainers are not available."
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.
Rename DockerRequired to ContainerRequired Clean up stray references to "docker"
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.
I'm good with whatever wording we choose. I like the annotation name so I'm approving :)
I think we have a consensus, so I'm going to merge this. If you want any further changes, @rhusar, please follow up with an issue. |
Agreed! Thanks. |
Rename DockerRequired to ContainerRequired
Clean up stray references to "docker"
Resolves #39.