[wildfly-dev] Re: Testing with Testcontainers, Arquillian and JUnit 5
I've updated the new test suite:
- remove base test classes (thanks @Jan Kašík for being picky here)
- introduce local mode (using a local browser)
- adjust package names to make it easier to interop with the existing test suite
- update README.md
// Harald
On Fri, Feb 4, 2022 at 12:43 PM Harald Pehl <hpehl(a)redhat.com> wrote:
On Fri, Feb 4, 2022 at 11:44 AM Jan Kašík <jkasik(a)redhat.com> wrote:
>
> I observed initialization taking place with each test class.
>
The WildFly container should be started / stopped before / after each unit test,
but the browser and HAL container should be started only once.
If your experience is different, let me know, the I should take a closer look.
>
> IMO it can add up to tens of minutes to the run.
>
On GitHub Actions the WildFly container starts in under 10 seconds, which is
ok for me.
>
> It always starts with a few lines of code and ends up in a pile of mess. :) I'm
really not a fan of inheritance in case of test classes since I spent some time trying to
resolve issues caused by this.
>
I think it's a trade-off. If you really don't like it, I can try to
use composition over inheritance.
>
> There's also another thing which I thought of. The host OS on CI machines might
be RHEL 8 where docker is not available. Do you also plan to document within this effort
how to run tests with podman?
>
I'll try to find resources on how to run w/o docker. I know there are
some discussions, issues
and PRs on the Testcontainers repo.