I think having the functional testing using H2 and then we can add a layer of
integration tests that run (weekly) using real instances (containerized or
otherwise).
H2 can at least certify the dialects of most databases which is the majority of
the differences as the overall usage of SQL is ver
+1
The utests should move more torward pure white-box tests if anything.
The easiest next-step/path-forward sounds like replacing Derby with an
alternative like H2.
Art
On Fri, Sep 26, 2025 at 1:02 AM Jean-Baptiste Onofré
wrote:
> That's a good point.
>
> I think it's useful in itests, but n
That's a good point.
I think it's useful in itests, but not in utests. For utests, I would
also prefer "in-memory" or "file" db (embedded).
Regards
JB
On Fri, Sep 26, 2025 at 9:37 AM Domenico Francesco Bruscino
wrote:
>
> The tests that depend on containers don't work well in containerized CI/C
The tests that depend on containers don't work well in containerized CI/CD
pipelines. I'd use a container for a test only if there are no other
alternatives.
Regards,
Domenico
On Fri, 26 Sept 2025 at 07:28, Jean-Baptiste Onofré wrote:
> For context, here's the example of using TestContainers wi
For context, here's the example of using TestContainers with reusable
container: you just define this URL on a datasource:
jdbc:tc:mysql:8.0.36:///databasename?TC_REUSABLE=true
tc == test container
Then, the testcontainer can use the same MySQL container across all
tests using this URL.
Just fy
The profile approach is doable. Just a couple of thoughts to add:
- Real unit tests are whitebox-only. If we are using any type of DB,
that's grey box or black box testing.
- The majority of our "unit tests" are actually grey box integration
tests.
- Using docker to spin up
I agree on TestContainers. There are ways to work around the lack of a
straight-forward lifecycle fit for TestContainers, but we can do well with
the docker-maven-plugin instead.
And personally, I think it is fine for the tests to require docker.
Art
On Thu, Sep 25, 2025 at 3:12 AM Clebert Suc
The docker-based integration tests could be added using a different maven
profile (ie -Pintegration-tests) and we can configure CI to only run that
profile weekly to keep the unit test execution time manageable.
-Matt
> On Sep 25, 2025, at 1:28 AM, Francois Papon
> wrote:
>
> Hi,
>
> For us
It's possible to reuse the same docker container across multiple tests
(shared mode).
On Thu, Sep 25, 2025 at 12:10 PM Clebert Suconic
wrote:
>
> Docker is an option, but I don't think TestContainers would be a good
> option. I would rather use a real docker and reuse the database among
> the who
sadly seems derby would never become a modern project before it get retired.
svn, yuck.
if there be people migrate it to git and put it to github maybe it can live
longer, but a svn server on apache.org? Come on no new people would like to
join the party.
Francois Papon 于2025年9月25日周四 18:53写道：
>
Hi,
For using both testcontainer and H2 I would prefer to use H2 if possible
because testcontainer can slow down the build/test and it's not always
available on CI runners because as runners can be a docker, running a
docker in a docker can be blocked for security reason.
regards,
François
Hi
Thanks for your message Clebert.
We are not in the rush but worth to explore the alternatives.
I think we have two options (for both Artemis and Classic):
1. Find another file db like h2
2. Use test containers
My preference is for 2 as the tests should be more accurate using a “real”
databas
from what I spoke to folks on slack channel, Derby is not really
mission critical for us. We could replace by HSQLDB / H2, or just use
a dockerized database.
For Artemis this is exactly what I'm planning to do.. use real databases.
I will say on the Derby community that we could replace it by
s
so, I spoke to folds on our slack channel for ActiveMQ.
We use for our testsute, and never in production... We can easily
replace it by either dockerized databases (e.g Mysql or Oracle), or
use HSQL / H2.
We would be happy to use it if there's still a community around it,
but if there's not enoug
14 matches
Mail list logo
