Just to close out on this issue -- we have tests working now. The intent was
always to refactor into Junit tests in any case -- and these are getting fired
correctly.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.o
Thanks for all the replies
I did try the test project from @tibordigana which worked well. I was able to
change names etc and still have the tests working, but oddly could still not
figure out why my main project was failing to find all the correct classes &
methods.
I ended up abandoning tryi
Hi Nigel,
I wrote a project for you
https://github.com/Tibor17/pojo-testing
It is related to the JUnit POJO testing with Maven Failsafe Plugin.
I guess you did not use the expected postfix. That's why there were 0 tests
to run.
Additionally, README file shows the command line example with filteri
On 2020/07/02 19:08:26, Nigel Jones wrote:
> What is odd though is that the class 'GlossaryFVT' itself isn't showing up in
> the Tests run line -- even with the includes in place. Yet other files like
> 'FVTContants' are. This I don't understand - before I get to the methods
> (though once
On 2020/07/02 18:23:13, Piotr Żygieło wrote:
> In plugin I only define executions (i.e. have no redefined includes),
> and test classes follow convention *IT (like SimpleIT).
Thanks
> When I change my method to static I get similar result to your log:
>
> > [INFO] Running
> > org.odpi.ope
> > > public static void testGlossary()
> > > {
> >
> > POJO ITs work in my set up, but my test methods are not static.
>
> Thanks. Can I check what naming convention you've used for your test methods
> -- and/or configuration to override this? How about your classes?
In plugin I only de
On 2020/07/02 17:39:25, Piotr Żygieło wrote:
> >
> > public static void testGlossary()
> > {
>
> POJO ITs work in my set up, but my test methods are not static.
Thanks. Can I check what naming convention you've used for your test methods --
and/or configuration to override this? H
>
> public static void testGlossary()
> {
POJO ITs work in my set up, but my test methods are not static.
--
Piotrek
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h
On 2020/07/02 17:10:08, Bernd Eckenfels wrote:
> The failsafe IntegrationTestMojo essentially is the surefire plugin (but with
> a different error lifecycle handled by the verifyMojo) and a different
> default include filter.
>
> https://github.com/apache/maven-surefire/blob/master/maven-f
much
about spring testing but I would asume such a thing already exists.
Gruss
Bernd
--
http://bernd.eckenfels.net
Von: Nigel Jones
Gesendet: Thursday, July 2, 2020 6:37:42 PM
An: users@maven.apache.org
Betreff: maven failsafe plugin & POJO tests
I have some &#x
I have some 'integration' tests that have been written as POJOs. They run
manually
I'm looking at refactoring to automate, making use of the failsafe plugin,
together with a few other plugins to launch a server process, and configure the
server against which the integration tests run.
I'm stru
11 matches
Mail list logo
