Integration testing: Experimentation with Arquillian and Testcontainers
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 564
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 29
Description
During the development of #9229 it became more and more evident that to create an integration test for this kind of functionality, we need a different setup of testing than our well known "unit tests + API tests".
This issue is a collection of ideas and experimentation to introduce more advanced integration testing using container technology (Docker) and frameworks like Testcontainers and Arquillian.
Doc links:
- https://docs.payara.fish/community/docs/Technical%20Documentation/Ecosystem/Connector%20Suites/Arquillian%20Containers/Payara%20Server%20Remote.html
- https://dzone.com/articles/integration-tests-with-arquillian-extensions-on-the-payara-platform
- https://github.com/arquillian/arquillian-core/issues/388
- https://github.com/hantsy/arquillian-autodeployment-example
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading issue #9229 and the existing unit and API test setup, then review the linked Arquillian and Testcontainers documentation. The issue is exploratory, so completion would require an agreed integration-testing approach and a concrete experiment using the proposed container-based tools.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, java
- Domain
- devops, testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 18/100