; > Hello,
> >
> > I was talking to Luca a while ago where he pointed me to this discussion
> on
> > StackOverflow [1]. This reminded me that last year I raised this
> suggestion
> > about deprecating some of the camel-testcontainers components. I think we
> > ha
On Tue, Feb 8, 2022 at 9:32 AM Otavio Rodolfo Piske
wrote:
>
> Hello,
>
> I was talking to Luca a while ago where he pointed me to this discussion on
> StackOverflow [1]. This reminded me that last year I raised this suggestion
> about deprecating some of the camel-testcontai
Hello,
I was talking to Luca a while ago where he pointed me to this discussion on
StackOverflow [1]. This reminded me that last year I raised this suggestion
about deprecating some of the camel-testcontainers components. I think we
have migrated all of our code to test-infra by now.
I am
://github.com/apache/camel/tree/master/test-infra
Kind regards
On Fri, Jan 8, 2021 at 10:00 AM Alexandre Gallice
wrote:
> I see no show stopper to deprecation.
> Some camel-testcontainers-junit5 users out in the community might enjoy a
> short and concise migration guide with explana
I see no show stopper to deprecation.
Some camel-testcontainers-junit5 users out in the community might enjoy a
short and concise migration guide with explanation from Otavio above.
On Fri, Jan 8, 2021 at 9:00 AM Andrea Cosentino wrote:
> I'm ok with deprecating the classes :-)
>
ned removing them before the next LTS, but,
> > indeed, this may be way too soon.
> >
> > Kind regards
> >
> > On Thu, Jan 7, 2021 at 2:49 PM Andrea Cosentino
> wrote:
> >
> >> I use test-infra stuff even at ckc but before deprecating the
> >&g
ra stuff even at ckc but before deprecating the
>> testcontainers components I'd like to have feedback from existing users..
>>
>> Il mar 5 gen 2021, 11:36 Otavio Rodolfo Piske ha
>> scritto:
>>
>> > Thanks Claus! That's a good point and I haven't writ
, 2021 at 2:49 PM Andrea Cosentino wrote:
> I use test-infra stuff even at ckc but before deprecating the
> testcontainers components I'd like to have feedback from existing users..
>
> Il mar 5 gen 2021, 11:36 Otavio Rodolfo Piske ha
> scritto:
>
> > Thanks Claus! That
I use test-infra stuff even at ckc but before deprecating the
testcontainers components I'd like to have feedback from existing users..
Il mar 5 gen 2021, 11:36 Otavio Rodolfo Piske ha
scritto:
> Thanks Claus! That's a good point and I haven't written much - other than
> th
camel/component/pg/replication/slot/integration/PgReplicationTestSupport.java#L31
13. https://github.com/apache/camel/pull/4706/files
On Tue, Jan 5, 2021 at 10:36 AM Claus Ibsen wrote:
> Hi Otavia
>
> Great work.
>
> Can you maybe tell a bit about what if an end user have used
> ca
Hello,
I think it's probably too early to deprecate testcontainers modules,
because test-infra modules are probably less easy to use currently.
I would leave them without deprecation for the moment.
But lets wait for more feedback.
Il giorno mar 5 gen 2021 alle ore 10:36 Claus Ibse
Hi Otavia
Great work.
Can you maybe tell a bit about what if an end user have used
camel-testcontainers-junit5 to do his/her own container testing with
Camel (for example to use their own container image, or for example a
database container or something). How would they do that today with
the
tests from Localstack containers to an actual AWS instance by simply
adjusting the test parameters. It still uses testcontainers under the hood,
but it is abstracted from the test code.
As result of this migration, the code in the following components has
become unused within Camel:
- camel-test
No problem, I just wanted to fix the build on builds.apache.org:
e.g.:
https://builds.apache.org/view/C/view/Apache%20Camel/job/Camel/job/master/623/console
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal
on project camel-testcontainers:
Could not resolve
it to branch master
in repository https://gitbox.apache.org/repos/asf/camel.git
The following commit(s) were added to refs/heads/master by this push:
new ad8308c Revert "Upgrade TestContainers to version 1.9.0", because
"org.testcontainers:testcontainers:jar:1.9.0" is
-1330 to be merged to get
surefire support?
Den ons. 23. mai 2018 kl. 10:08 skrev Zoran Regvart :
Hi,
on the testcontainers thread I mentioned that we can switch to JUnit5.
I've attended a talk by Sam Brannen at the local JUG. I think it was a
variant of the talk[1] he gave at SpringOne
for
> > https://issues.apache.org/jira/browse/SUREFIRE-1330 to be merged to get
> > surefire support?
> >
> > Den ons. 23. mai 2018 kl. 10:08 skrev Zoran Regvart :
> >
> >> Hi,
> >> on the testcontainers thread I mentioned that we can switch to JUnit5.
> &g
Github user lburgazzoli closed the pull request at:
https://github.com/apache/camel/pull/2362
---
GitHub user lburgazzoli opened a pull request:
https://github.com/apache/camel/pull/2362
CAMEL-12534: create camel-testcontainers
Initial bits of testcontainers integration with camel test suite.
### WHAT'S NEW
- two new modules:
- camel-testconta
mage would have helped
> in testing a regular camel component.
> Would it be in the scope of camel-testcontainers ? I mean building a custom
> image, pushing it to docker hub and use that for route level tests of a
> regular component ?
>
> Alex
>
>
>
> On Wed, May
Hi Luca,
+1 as you demonstrated the use to test starters.
I already faced a situation where a custom docker image would have helped
in testing a regular camel component.
Would it be in the scope of camel-testcontainers ? I mean building a custom
image, pushing it to docker hub and use that
v Zoran Regvart :
>
>> Hi,
>> on the testcontainers thread I mentioned that we can switch to JUnit5.
>> I've attended a talk by Sam Brannen at the local JUG. I think it was a
>> variant of the talk[1] he gave at SpringOne 2017.
>>
>> The key takeaway for m
Would you have to await for
https://issues.apache.org/jira/browse/SUREFIRE-1330 to be merged to get
surefire support?
Den ons. 23. mai 2018 kl. 10:08 skrev Zoran Regvart :
> Hi,
> on the testcontainers thread I mentioned that we can switch to JUnit5.
> I've attended a talk by Sam
Hi,
on the testcontainers thread I mentioned that we can switch to JUnit5.
I've attended a talk by Sam Brannen at the local JUG. I think it was a
variant of the talk[1] he gave at SpringOne 2017.
The key takeaway for me was that JUnit5 is forward and backward
compatible, so you can run the
; > I would also consider marking those as integration tests so they are
>>> > run only if we want them to be run, or in environments that we know
>>> > they'll run without issues.
>>> >
>>>
>>> As first iteration I'd use profiles, jun
n only if we want them to be run, or in environments that we know
>> > they'll run without issues.
>> >
>>
>> As first iteration I'd use profiles, junit 5 is not exatly as easy as
>> junit 4 is.
>>
>> > zoran
>> >
>>
un only if we want them to be run, or in environments that we know
> > they'll run without issues.
> >
>
> As first iteration I'd use profiles, junit 5 is not exatly as easy as
> junit 4 is.
>
> > zoran
> >
> > On Tue, May 22, 2018 at 5:35 PM, Luca
gt;
> On Tue, May 22, 2018 at 5:35 PM, Luca Burgazzoli
> wrote:
>> Hi all,
>>
>> I've been using testcontainers [1] for a while and I found it useful
>> to test against non java services such as consul, etcd and so on so
>> I'd like to create a camel-testc
+1
On Tue, May 22, 2018 at 5:35 PM, Luca Burgazzoli wrote:
> Hi all,
>
> I've been using testcontainers [1] for a while and I found it useful
> to test against non java services such as consul, etcd and so on so
> I'd like to create a camel-testcontainers "c
ool that we can start the container in the Java unit test.
> >
> > @Luca
> > Could you provide a typic use case(with code) of using
> camel-testcontainers?
> > Normally, we just need to spin up the service image for the testing, I
> > think testcontainer already provi
23, 2018 at 12:35 AM, Willem Jiang wrote:
> Hi
>
> I just go through the test container introduction,
> it's cool that we can start the container in the Java unit test.
>
> @Luca
> Could you provide a typic use case(with code) of using camel-testcontainers?
> Normally,
Hi
I just go through the test container introduction,
it's cool that we can start the container in the Java unit test.
@Luca
Could you provide a typic use case(with code) of using camel-testcontainers?
Normally, we just need to spin up the service image for the testing, I
think testcont
them to be run, or in environments that we know
they'll run without issues.
zoran
On Tue, May 22, 2018 at 5:35 PM, Luca Burgazzoli wrote:
> Hi all,
>
> I've been using testcontainers [1] for a while and I found it useful
> to test against non java services such as consul, e
Yes test only, sometimes you do not have a java test framework to spin
up an instance of the target service you want to integrate so having
some support in camel to spin up a containerized service may be
useful. I used testcontainers to test etcd and consul and by spinning
up a container for the
>
> Thanks,
> Paul
>
> On Tue, May 22, 2018 at 11:35 AM, Luca Burgazzoli
> wrote:
>
>> Hi all,
>>
>> I've been using testcontainers [1] for a while and I found it useful
>> to test against non java services such as consul, etcd and so on so
>>
What would be some example use cases that illustrate the need to manage
containers using Camel in particular? Just testing only?
Thanks,
Paul
On Tue, May 22, 2018 at 11:35 AM, Luca Burgazzoli
wrote:
> Hi all,
>
> I've been using testcontainers [1] for a while and I found it us
Great idea! +1
Il mar, 22 mag, 2018 alle 17:35, Luca Burgazzoli ha
scritto: Hi all,
I've been using testcontainers [1] for a while and I found it useful
to test against non java services such as consul, etcd and so on so
I'd like to create a camel-testcontainers "component
Hi all,
I've been using testcontainers [1] for a while and I found it useful
to test against non java services such as consul, etcd and so on so
I'd like to create a camel-testcontainers "component" that includes
some facilities like a dedicated test support that take care
38 matches
Mail list logo
