Hi Folks,
Any idea if we can run tests using the Jupiter engine of JUnit 5 with
Arquillian on TomEE?
Has anyone tried it?
Cheers
--
Bruno Baptista
https://twitter.com/brunobat_
AFAIK Arquillian itself is still not compatible with JUnit5?!
Am Mo., 11. März 2019 um 19:15 Uhr schrieb Bruno Baptista <
bruno...@gmail.com>:
> Hi Folks,
>
> Any idea if we can run tests using the Jupiter engine of JUnit 5 with
> Arquillian on TomEE?
>
> Has anyone tried it?
>
> Cheers
>
> --
>
Hey Bruno,
I don't know and did not try yet.
What does it bring out of curiosity?
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com
On Mon, Mar 11, 2019 at 7:15 PM Bruno Baptista wrote:
> Hi Folks,
>
> Any idea if we can run tests using the Jupiter engine of JUn
Hi Jean-Louis,
I'm hacking a comparison between multiple frameworks and all apart from
Arquillian seem to support JUnit 5 already.
I was hopping to be missing something, but it seems it's not supported yet.
Cheers
Bruno Baptista
https://twitter.com/brunobat_
On 11/03/19 18:22, Jean-Louis M
No, it is not supported.
Missatge de Bruno Baptista del dia dl., 11 de març
2019 a les 19:28:
> Hi Jean-Louis,
>
> I'm hacking a comparison between multiple frameworks and all apart from
> Arquillian seem to support JUnit 5 already.
>
> I was hopping to be missing something, but it seems it's no
Thanks for the help Thomas, Jean-Louis and Alex!
Bruno Baptista
https://twitter.com/brunobat_
On 11/03/19 18:32, Alex Soto wrote:
No, it is not supported.
Missatge de Bruno Baptista del dia dl., 11 de març
2019 a les 19:28:
Hi Jean-Louis,
I'm hacking a comparison between multiple framewor
Hi All!
2 years have passed. Any news about this?
Can we now test with Arquillian and TomEE with JUnit 5?
Cheers
Bruno Baptista
https://twitter.com/brunobat_
--
Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
Hi Bruno,
I think Richard worked on it.
Not sure about the status, but as far as I can recall, he created a ticket
(TomEE-2966: JUnit5 OpenEJB Extension Module) and a PR for it.
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com
On Sat, Mar 6, 2021 at 8:11 PM bruno
Hi all,
yes, I did some work related to JUnit5 for the old (legacy) code (via
InitialContext, see [1]), which shouldnt be used anymore but hinders
some users to migrate to JUnit5 (who are using the legacy approach).
This PR is merged into master and will be available with the next
release.
Howeve
Thanks Jean-Louis, Richard!
On 08/03/21 08:44, Richard Zowalla wrote:
Hi all,
yes, I did some work related to JUnit5 for the old (legacy) code (via
InitialContext, see [1]), which shouldnt be used anymore but hinders
some users to migrate to JUnit5 (who are using the legacy approach).
This PR
I did a quick check:
Arquillian is supporting JUnit 5 since 1.7.0-Alpha5. I created a Jira
[1] and added two examples (see PR @ [2]), which are using JUnit 5 only
for Arquillian-based testing.
ApplicationComposer relies on JUnit4 Code. Thus, a ApplicationComposer
JUnit5-Extension would be necessa
Hi @all,
we have some progress related to a pure JUnit 5 application composers
extension, see [1].
Would be good to get some additional feedback on it. Already received a
lot of valuable feedback by @rmannibucau (thx), which is already
incorporated in the current PR.
Gruss
Richard
- [1] https:
Hi all,
I went ahead and merged the changes. We are now capable of running
JUnit 5 tests via @RunWithApplicationComposer with some modes to
specify (container for each test method, for each test class, per jvm
or based on the JUnit 5 test instance lifecycle). Usage example can be
found in [1] and
> On Mar 23, 2021, at 1:45 PM, Zowalla, Richard
> wrote:
>
> Hi all,
>
> I went ahead and merged the changes. We are now capable of running
> JUnit 5 tests via @RunWithApplicationComposer with some modes to
> specify (container for each test method, for each test class, per jvm
> or based on th
14 matches
Mail list logo
