Blog post: Testing on Kubernetes with Arquillian Cube #742
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
fabiobrz
force-pushed
the
mini-series.k8s-cube
branch
from
a4ac878 to
b10396a
Compare
|
Hi @jamezp - could you please review this one? 🙏 |
bstansberry
requested changes
Mar 3, 2025
|
|
||
| That's cool!... but still, it is based on manual steps. | ||
|
|
||
| In order to do so, we'll modify the example application that we showcased in |
There was a problem hiding this comment.
s/do so/automate this/g
|
|
||
| As said, we will to start from the | ||
| https://www.wildfly.org/news/2025/01/27/testing-on-docker-with-cube/[Testing WildFly applications on Docker with Arquillian Cube] article, so make sure to go through it, and maybe create a separate Git repo, or branch if you want to keep working on | ||
| both the examples, then... |
| port: 9990 | ||
| ---- | ||
|
|
||
| and - rather than applying it manually to our _Minikube_ instance via a `kubectl` command, we'll let Arquillian Cube do the job! |
There was a problem hiding this comment.
s/command,/command -/g
or change the first ' -' to a comma.
| classpath. | ||
|
|
||
| If such a definition exists, then Arquillian Cube will apply it to the cluster, and it will provide us with APIs and | ||
| annotations at the class level, that we'll use to wire the test logic up, as we'll see later on. |
| A few changes, provided we started from the previous article about | ||
| https://www.wildfly.org/news/2025/01/27/testing-on-docker-with-cube/[Testing WildFly applications on Docker with Arquillian Cube]. | ||
|
|
||
| The first thing we need to do is to add a couple more property for two new dependency that we'll need to add, details |
There was a problem hiding this comment.
s/property/properties
s/dependency/dependencies
s/add,/add;/g
| ---- | ||
|
|
||
| Now, onto the (`<build>/<plugins>` section, first off we don't need for the `maven-clean-plugin` to clean up any | ||
| Docker files, in fact we'll remove those from our project sources later on, since this test will not build nor run any |
|
|
||
| Now, onto the (`<build>/<plugins>` section, first off we don't need for the `maven-clean-plugin` to clean up any | ||
| Docker files, in fact we'll remove those from our project sources later on, since this test will not build nor run any | ||
| Docker images, let's comment the section as follows: |
There was a problem hiding this comment.
s/images, let's/images. Let's/g
|
|
||
| === Remove the application sources | ||
|
|
||
| Again, we're not building any application here, we rely on a DOcker image on Quay, that contains the application |
There was a problem hiding this comment.
s/here, we/here. We/g
s/DOcker/Docker/g
s/Quay,/Quay/g
| === Remove the application sources | ||
|
|
||
| Again, we're not building any application here, we rely on a DOcker image on Quay, that contains the application | ||
| already, therefore we don't need the application sources, which can be safely removed: |
| we verify that the service - which is implemented by a Kubernetes workload - returns HTTP 200 and the expected response | ||
| body when it is called via its URL. | ||
|
|
||
| And that is where Arquillian Cube comes in handy because, thanks to it, we could inject such URL in our test class |
There was a problem hiding this comment.
s/such URL/such a URL/g
fabiobrz
force-pushed
the
mini-series.k8s-cube
branch
from
b10396a to
9196cb6
Compare
Thanks for your review @bstansberry ! Hopefully I addressed your comments (and rebased, hence maybe not so easily visible, sorry about that). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
SSIA