[Announce] Tapestry Testify project

[Paul Field-3]

I'd like to announce that the Tapestry Testify project is now available as a
Snapshot release at Tapestry 360:
https://tapestry.formos.com/nightly/tapestry-testify/

Tapestry Testify is an extension to Tapestry that allows you to write page
and component tests very easily and have them run very efficiently.


** Features **

  Integration with JUnit3 , JUnit4 and TestNG

  Per-test scope - define services that are re-created for each test

  Inject services into tests with the @Inject annotation

  Inject objects from the test into components with the @ForComponent
annotation

  Very efficient - allows a single PageTester to be used by all tests


Fedback is very welcome!

- Paul

---
Paul Field
http://creakingcogs.blogspot.com/


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[Angelo Chen]

definately a good addition, I tested only services now, I gave up the PageTester, it's not practical to use it, and yet to learn that Integrated test, I have been looking for a way to test pages and components, will give your Testify, hope it will not be like PageTester:)

Paul Field-3 wrote:

I'd like to announce that the Tapestry Testify project is now available as a
Snapshot release at Tapestry 360:
https://tapestry.formos.com/nightly/tapestry-testify/

Tapestry Testify is an extension to Tapestry that allows you to write page
and component tests very easily and have them run very efficiently.


** Features **

  Integration with JUnit3 , JUnit4 and TestNG

  Per-test scope - define services that are re-created for each test

  Inject services into tests with the @Inject annotation

  Inject objects from the test into components with the @ForComponent
annotation

  Very efficient - allows a single PageTester to be used by all tests


Fedback is very welcome!

- Paul

---
Paul Field
http://creakingcogs.blogspot.com/


---------------------------------------------------------------------
To unsubscribe, e-mail: [e-mail]
For additional commands, e-mail: [e-mail]

[P.Stavrinides]

This looks really promising Paul, thanks!

One question, can Easymock be used for mocks, I am not familiar with Mockito?

cheers,
Peter

----- Original Message -----
From: "Angelo Chen" <angelochen960@...>
To: users@...
Sent: Friday, 19 June, 2009 06:57:55 GMT +02:00 Athens, Beirut, Bucharest, Istanbul
Subject: Re: [Announce] Tapestry Testify project


definately a good addition, I tested only services now, I gave up the
PageTester, it's not practical to use it, and yet to learn that Integrated
test, I have been looking for a way to test pages and components, will give
your Testify, hope it will not be like PageTester:)


Paul Field-3 wrote:

>
> I'd like to announce that the Tapestry Testify project is now available as
> a
> Snapshot release at Tapestry 360:
> https://tapestry.formos.com/nightly/tapestry-testify/
>
> Tapestry Testify is an extension to Tapestry that allows you to write page
> and component tests very easily and have them run very efficiently.
>
>
> ** Features **
>
>   Integration with JUnit3 , JUnit4 and TestNG
>
>   Per-test scope - define services that are re-created for each test
>
>   Inject services into tests with the @Inject annotation
>
>   Inject objects from the test into components with the @ForComponent
> annotation
>
>   Very efficient - allows a single PageTester to be used by all tests
>
>
> Fedback is very welcome!
>
> - Paul
>
> ---
> Paul Field
> http://creakingcogs.blogspot.com/
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@...
> For additional commands, e-mail: users-help@...
>
>
>

--
View this message in context: http://www.nabble.com/-Announce--Tapestry-Testify-project-tp24102834p24105144.html
Sent from the Tapestry - User mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[Paul Field-4]

> This looks really promising Paul, thanks!
>
> One question, can Easymock be used for mocks, I am not familiar with
Mockito?

Absolutely - Testify doesn't depend on Mockito.

BTW, do look at Mockito (http://mockito.org/) - it's a very clean way to
write stubs and mocks - I used to be an EasyMock user and I've been
converted :-)


So, some more information (which I will put into the documentation at some
point) ....

My aim was just made sure that Testify would work well with Mockito's
@Mock annotation so, if you use Mockito, it's *really* simple to create a
mock and inject it into a component:

public class MyTest extends AbstractMyApplicationTest {
    @ForComponents @Mock MyService service;
 
    public void testElementIsOnPage() {
        when(service.shouldShowElement()).thenReturn(true);
        Document page = tester.renderPage("mypage");
        assertNotNull(page.getElementById("myid"));
    }

In this example, @ForComponents is a Testify annotation; @Mock is a
Mockito annotation and AbstractMyApplicationTest is your own abstract test
class that does standard setup:

public abstract class AbstractMyApplicationTest extends TapestryTest {
    private static final TapestryTester SHARED_TESTER
        = new TapestryTester("demo", MyCoreModule.class);

    public TestifyTest() {
        super(SHARED_TESTER);
    }
 
    @Override
    protected void setUpForAllTestClasses() throws Exception {
        MockitoAnnotations.initMocks(this);
    }
}

Because this is *your* standard superclass, it's your choice to include
other frameworks such as Mockito (or you could write your own equivalent
of @Mock but for EasyMock and wire it in here).

-------------------------

However, if you wanted to use EasyMock, you'd setup the mocks yourself in
your test. Something like this:

public class MyTest extends AbstractMyApplicationTest {
    @ForComponents MyService service;
 
    public void doSetUp() {
        service = EasyMock.createMock(MyService.class);
    }

    public void testElementIsOnPage() {
        expect(service.shouldShowElement()).andReturn(true);
        replay(service);
        Document page = tester.renderPage("mypage");
        assertNotNull(page.getElementById("myid"));
    }


And your standard superclass, obviously, doesn't set up Mockito:

public abstract class AbstractMyApplicationTest extends TapestryTest {
    private static final TapestryTester SHARED_TESTER
        = new TapestryTester("demo", MyCoreModule.class);

    public TestifyTest() {
        super(SHARED_TESTER);
    }
}

------------------
Paul Field
Research IT
Deutsche Bank




---

This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and delete this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.

Please refer to http://www.db.com/en/content/eu_disclosures.htm for additional EU corporate and regulatory disclosures.

[Paul Field-4]

Hi Angelo,

> definately a good addition, I tested only services now, I gave up the
> PageTester, it's not practical to use it, and yet to learn that
Integrated
> test, I have been looking for a way to test pages and components, will
give
> your Testify, hope it will not be like PageTester:)

That's exactly why I wrote Testify. PageTester is good but it's slow to
create one (I was finding about 4secs for the first instances and about
2secs for each other instance) and I was finding I needed different
instances for different tests - so my tests were taking ages to run. Also
it was very difficult to use mocks in the tests.

So Testify takes advantage of all the good infrastructure in PageTester
but makes it very fast because you can share one TapestryTester (which is
just a subclass of PageTester) amongst all your tests - so you just get a
one-off startup cost and then all the other tests are free.

I also added in facilities to make using Mocks very simple and that plus
the speed means it's practical to do lots of small-scale tests in the TDD
style.

Hopefully you'll find it's just what you were looking for :-)  And if not,
let me know the problem and I'll try to fix it.

Paul

------------------
Paul Field
Research IT
Deutsche Bank



---

This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and delete this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.

Please refer to http://www.db.com/en/content/eu_disclosures.htm for additional EU corporate and regulatory disclosures.

[Angelo Chen]

Hi Paul,

Cool, will try that out over the weekend, T5 really needs a easy to use testing framework for pages and component, if can be used for TDD, that's even better. will get back to you after I try it out, thanks and keep me updated about Testify(the name sounds good!)

Angelo

Paul Field wrote:

Hi Angelo,

> definately a good addition, I tested only services now, I gave up the
> PageTester, it's not practical to use it, and yet to learn that
Integrated
> test, I have been looking for a way to test pages and components, will
give
> your Testify, hope it will not be like PageTester:)

That's exactly why I wrote Testify. PageTester is good but it's slow to
create one (I was finding about 4secs for the first instances and about
2secs for each other instance) and I was finding I needed different
instances for different tests - so my tests were taking ages to run. Also
it was very difficult to use mocks in the tests.

So Testify takes advantage of all the good infrastructure in PageTester
but makes it very fast because you can share one TapestryTester (which is
just a subclass of PageTester) amongst all your tests - so you just get a
one-off startup cost and then all the other tests are free.

I also added in facilities to make using Mocks very simple and that plus
the speed means it's practical to do lots of small-scale tests in the TDD
style.

Hopefully you'll find it's just what you were looking for :-)  And if not,
let me know the problem and I'll try to fix it.

Paul

------------------
Paul Field
Research IT
Deutsche Bank



---

This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and delete this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.

Please refer to http://www.db.com/en/content/eu_disclosures.htm for additional EU corporate and regulatory disclosures.

[P.Stavrinides]

I have very briefly tried to get this up and running (using JUnit 4), but I am not sure what to make of the example, although the instructions seem simple enough, could there be a naming problem in the constructor, shouldn't it read:

import com.formos.tapestry.testify.core.TapestryTester;
import com.formos.tapestry.testify.junit4.TapestryTest;

public abstract class AbstractMyApplicationTest extends TapestryTest {
    private static final TapestryTester SHARED_TESTER = new TapestryTester("demo", MyCoreModule.class);

    public *AbstractMyApplicationTest()* {  //and not TestifyTest() ?
        super(SHARED_TESTER);
    }
   
    @Override
    protected void setUpForAllTestClasses() throws Exception {
        MockitoAnnotations.initMocks(this);
    }    
}

Cheers,
Peter

----- Original Message -----
From: "Paul Field" <paul.field@...>
To: "Tapestry users" <users@...>
Sent: Friday, 19 June, 2009 11:53:24 GMT +02:00 Athens, Beirut, Bucharest, Istanbul
Subject: Re: [Announce] Tapestry Testify project

> This looks really promising Paul, thanks!
>
> One question, can Easymock be used for mocks, I am not familiar with
Mockito?

Absolutely - Testify doesn't depend on Mockito.

BTW, do look at Mockito (http://mockito.org/) - it's a very clean way to
write stubs and mocks - I used to be an EasyMock user and I've been
converted :-)


So, some more information (which I will put into the documentation at some
point) ....

My aim was just made sure that Testify would work well with Mockito's
@Mock annotation so, if you use Mockito, it's *really* simple to create a
mock and inject it into a component:

public class MyTest extends AbstractMyApplicationTest {
    @ForComponents @Mock MyService service;
 
    public void testElementIsOnPage() {
        when(service.shouldShowElement()).thenReturn(true);
        Document page = tester.renderPage("mypage");
        assertNotNull(page.getElementById("myid"));
    }

In this example, @ForComponents is a Testify annotation; @Mock is a
Mockito annotation and AbstractMyApplicationTest is your own abstract test
class that does standard setup:

public abstract class AbstractMyApplicationTest extends TapestryTest {
    private static final TapestryTester SHARED_TESTER
        = new TapestryTester("demo", MyCoreModule.class);

    public TestifyTest() {
        super(SHARED_TESTER);
    }
 
    @Override
    protected void setUpForAllTestClasses() throws Exception {
        MockitoAnnotations.initMocks(this);
    }
}

Because this is *your* standard superclass, it's your choice to include
other frameworks such as Mockito (or you could write your own equivalent
of @Mock but for EasyMock and wire it in here).

-------------------------

However, if you wanted to use EasyMock, you'd setup the mocks yourself in
your test. Something like this:

public class MyTest extends AbstractMyApplicationTest {
    @ForComponents MyService service;
 
    public void doSetUp() {
        service = EasyMock.createMock(MyService.class);
    }

    public void testElementIsOnPage() {
        expect(service.shouldShowElement()).andReturn(true);
        replay(service);
        Document page = tester.renderPage("mypage");
        assertNotNull(page.getElementById("myid"));
    }


And your standard superclass, obviously, doesn't set up Mockito:

public abstract class AbstractMyApplicationTest extends TapestryTest {
    private static final TapestryTester SHARED_TESTER
        = new TapestryTester("demo", MyCoreModule.class);

    public TestifyTest() {
        super(SHARED_TESTER);
    }
}

------------------
Paul Field
Research IT
Deutsche Bank




---

This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and delete this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.

Please refer to http://www.db.com/en/content/eu_disclosures.htm for additional EU corporate and regulatory disclosures.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[Paul Field-4]

P.Stavrinides@... wrote on 19/06/2009 17:00:14:

> could there be a naming problem in
> the constructor, shouldn't it read:
>
> public abstract class AbstractMyApplicationTest extends TapestryTest {
.....
>     public *AbstractMyApplicationTest()* {  //and not TestifyTest() ?
>         super(SHARED_TESTER);
>     }
...


Hi Peter,

Doh! Yes - I renamed the classes in the documentation and forgot to rename
the constructors... thanks for pointing that out.

I'll fix the documentation when I'm at home - it will be in the next
nightly build.

Paul

------------------
Paul Field
Research IT
Deutsche Bank



---

This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and delete this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.

Please refer to http://www.db.com/en/content/eu_disclosures.htm for additional EU corporate and regulatory disclosures.

[P.Stavrinides]

Hi Paul,

I seem to be too stupid to get testify working with JUnit 4, I can't get even past the gate:

java.lang.NoClassDefFoundError: Could not initialize class com.albourne.web.testinfrastructure.TestMailService
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at org.junit.internal.runners.BeforeAndAfterRunner.invokeMethod(BeforeAndAfterRunner.java:74)
        at org.junit.internal.runners.BeforeAndAfterRunner.runAfters(BeforeAndAfterRunner.java:65)
        at org.junit.internal.runners.BeforeAndAfterRunner.runProtected(BeforeAndAfterRunner.java:37)
        at org.junit.internal.runners.TestClassRunner.run(TestClassRunner.java:52)
        at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:38)
        at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
        at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460)
        at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673)
        at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386)
        at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196)

I get this regardless of what I try, its being caused by:
private static final TapestryTester SHARED_TESTER = new TapestryTester("demo", MyCoreModule.class);

... I am not sure exactly what this relates to, especially without source. Any suggestions?

Cheers,
Peter

----- Original Message -----
From: "Paul Field" <paul.field@...>
To: "Tapestry users" <users@...>
Sent: Monday, 22 June, 2009 12:07:02 GMT +02:00 Athens, Beirut, Bucharest, Istanbul
Subject: Re: [Announce] Tapestry Testify project

P.Stavrinides@... wrote on 19/06/2009 17:00:14:

> could there be a naming problem in
> the constructor, shouldn't it read:
>
> public abstract class AbstractMyApplicationTest extends TapestryTest {
.....
>     public *AbstractMyApplicationTest()* {  //and not TestifyTest() ?
>         super(SHARED_TESTER);
>     }
...


Hi Peter,

Doh! Yes - I renamed the classes in the documentation and forgot to rename
the constructors... thanks for pointing that out.

I'll fix the documentation when I'm at home - it will be in the next
nightly build.

Paul

------------------
Paul Field
Research IT
Deutsche Bank



---

This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and delete this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.

Please refer to http://www.db.com/en/content/eu_disclosures.htm for additional EU corporate and regulatory disclosures.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[Paul Field-4]

P.Stavrinides@... wrote on 24/06/2009 15:35:00:

> I seem to be too stupid to get testify working with JUnit 4, I can't
> get even past the gate:

I prefer to see it as a failure of my documentation :-)

First thing, the Testify sources are published to the Maven repository, so
you can pick them up manually from:
http://tapestry.formos.com/maven-snapshot-repository/com/formos/tapestry/tapestry-testify/1.0.0-SNAPSHOT/

Or just ask Maven to download them for you:
mvn [goal] -DdownloadSources=true

(The m2eclipse plugin for eclipse can download them and bind them to the
jar for you, which makes life very pleasant).


Next, I think my documentation is misleading you... try:

private static final TapestryTester SHARED_TESTER = new
TapestryTester("demo");


The documentation's example with "MyCoreModule.class" is meant to show you
how to include your own "core" IOC module
(see:
http://tapestry.formos.com/nightly/tapestry-testify/#Integration_testing 
).

Alternatively, you might need to include your AppModule as the parameter -
if you do then read the link above about integration testing
and break up your AppModule.

Let me know how you get on!

Paul

------------------
Paul Field
Research IT
Deutsche Bank




---

This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and delete this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.

Please refer to http://www.db.com/en/content/eu_disclosures.htm for additional EU corporate and regulatory disclosures.

[P.Stavrinides]

Hi Paul,

Thanks for following up on this!

> Next, I think my documentation is misleading you... try:
> private static final TapestryTester SHARED_TESTER = new
> TapestryTester("demo");
Tried this with no luck

> The documentation's example with "MyCoreModule.class" is meant to show you
> how to include your own "core" IOC module
Right, and this is what I am doing, but with or without the IoC module I can't get it running, it fails inside TapestryTester?

>First thing, the Testify sources are published to the Maven repository
FYI I am using maven, Hmmm... I see now that there are sources in the repo, sorry my bad! I don't know why the sources are not being pulled on my side, I do use a nexus repository locally so there must be something going wrong there. I will try to get at the sources to figure out what is happening, I will let you know. Just curious if anyone has testify working with JUnit 4?

Thanks
Peter

----- Original Message -----
From: "Paul Field" <paul.field@...>
To: "Tapestry users" <users@...>
Sent: Wednesday, 24 June, 2009 18:44:30 GMT +02:00 Athens, Beirut, Bucharest, Istanbul
Subject: Re: [Announce] Tapestry Testify project

P.Stavrinides@... wrote on 24/06/2009 15:35:00:

> I seem to be too stupid to get testify working with JUnit 4, I can't
> get even past the gate:

I prefer to see it as a failure of my documentation :-)

First thing, the Testify sources are published to the Maven repository, so
you can pick them up manually from:
http://tapestry.formos.com/maven-snapshot-repository/com/formos/tapestry/tapestry-testify/1.0.0-SNAPSHOT/

Or just ask Maven to download them for you:
mvn [goal] -DdownloadSources=true

(The m2eclipse plugin for eclipse can download them and bind them to the
jar for you, which makes life very pleasant).


Next, I think my documentation is misleading you... try:

private static final TapestryTester SHARED_TESTER = new
TapestryTester("demo");


The documentation's example with "MyCoreModule.class" is meant to show you
how to include your own "core" IOC module
(see:
http://tapestry.formos.com/nightly/tapestry-testify/#Integration_testing 
).

Alternatively, you might need to include your AppModule as the parameter -
if you do then read the link above about integration testing
and break up your AppModule.

Let me know how you get on!

Paul

------------------
Paul Field
Research IT
Deutsche Bank




---

This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and delete this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.

Please refer to http://www.db.com/en/content/eu_disclosures.htm for additional EU corporate and regulatory disclosures.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[P.Stavrinides]

Hi Paul,

This is the cause:
java.lang.ClassNotFoundException: org.apache.tapestry5.test.TapestryTestConstants

bubbles up from from Pagetester line 111:
globals.storeContext(new PageTesterContext(contextPath));)

from PageTesterContext line 32:
 this.contextRoot = new File(TapestryTestConstants.MODULE_BASE_DIR, contextRoot);

What is TapestryTestConstants its not packaged with the jars? so I don't see how this can possibly work.

Kind regards,
Peter

----- Original Message -----
From: "P Stavrinides" <P.Stavrinides@...>
To: "Tapestry users" <users@...>
Sent: Thursday, 25 June, 2009 10:38:32 GMT +02:00 Athens, Beirut, Bucharest, Istanbul
Subject: Re: [Announce] Tapestry Testify project

Hi Paul,

Thanks for following up on this!

> Next, I think my documentation is misleading you... try:
> private static final TapestryTester SHARED_TESTER = new
> TapestryTester("demo");
Tried this with no luck

> The documentation's example with "MyCoreModule.class" is meant to show you
> how to include your own "core" IOC module
Right, and this is what I am doing, but with or without the IoC module I can't get it running, it fails inside TapestryTester?

>First thing, the Testify sources are published to the Maven repository
FYI I am using maven, Hmmm... I see now that there are sources in the repo, sorry my bad! I don't know why the sources are not being pulled on my side, I do use a nexus repository locally so there must be something going wrong there. I will try to get at the sources to figure out what is happening, I will let you know. Just curious if anyone has testify working with JUnit 4?

Thanks
Peter

----- Original Message -----
From: "Paul Field" <paul.field@...>
To: "Tapestry users" <users@...>
Sent: Wednesday, 24 June, 2009 18:44:30 GMT +02:00 Athens, Beirut, Bucharest, Istanbul
Subject: Re: [Announce] Tapestry Testify project

P.Stavrinides@... wrote on 24/06/2009 15:35:00:

> I seem to be too stupid to get testify working with JUnit 4, I can't
> get even past the gate:

I prefer to see it as a failure of my documentation :-)

First thing, the Testify sources are published to the Maven repository, so
you can pick them up manually from:
http://tapestry.formos.com/maven-snapshot-repository/com/formos/tapestry/tapestry-testify/1.0.0-SNAPSHOT/

Or just ask Maven to download them for you:
mvn [goal] -DdownloadSources=true

(The m2eclipse plugin for eclipse can download them and bind them to the
jar for you, which makes life very pleasant).


Next, I think my documentation is misleading you... try:

private static final TapestryTester SHARED_TESTER = new
TapestryTester("demo");


The documentation's example with "MyCoreModule.class" is meant to show you
how to include your own "core" IOC module
(see:
http://tapestry.formos.com/nightly/tapestry-testify/#Integration_testing 
).

Alternatively, you might need to include your AppModule as the parameter -
if you do then read the link above about integration testing
and break up your AppModule.

Let me know how you get on!

Paul

------------------
Paul Field
Research IT
Deutsche Bank




---

This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and delete this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.

Please refer to http://www.db.com/en/content/eu_disclosures.htm for additional EU corporate and regulatory disclosures.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[Paul Field-4]

Hi Peter,

> This is the cause:
> java.lang.ClassNotFoundException: org.apache.tapestry5.test.
> TapestryTestConstants
>
> What is TapestryTestConstants its not packaged with the jars? so I
> don't see how this can possibly work.

TapestryTestConstants is an object from org.apache.tapestry5.test:
http://tapestry.apache.org/tapestry5/apidocs/org/apache/tapestry5/test/TapestryTestConstants.html

So, you need to add a dependency on the tapestry-test module  (and I need
to check what's going on in the Testify POM because you should've got that
automatically... ).

This is the Maven dependency I suggest, as you probably don't want the
Selenium dependencies:

<dependency>
        <groupId>org.apache.tapestry</groupId>
        <artifactId>tapestry-test</artifactId>
        <version>${tapestry.version}</version>
        <scope>test</scope>
        <exclusions>
                <exclusion>
                        <groupId>org.openqa.selenium.client-drivers</
groupId>
                        <artifactId>selenium-java-client-driver</
artifactId>
                </exclusion>
                <exclusion>
                        <groupId>org.openqa.selenium.server</groupId>
                        <artifactId>selenium-server</artifactId>
                </exclusion>
                <exclusion>
                        <groupId>org.openqa.selenium.server</groupId>
                        <artifactId>selenium-server-coreless</artifactId>
                </exclusion>
        </exclusions>
</dependency>

FYI, I'm not convinced that you should have to have this dependency at
all. See:
https://issues.apache.org/jira/browse/TAP5-758

Paul
------------------
Paul Field
Research IT
Deutsche Bank

>
> Kind regards,
> Peter
>
> ----- Original Message -----
> From: "P Stavrinides" <P.Stavrinides@...>
> To: "Tapestry users" <users@...>
> Sent: Thursday, 25 June, 2009 10:38:32 GMT +02:00 Athens, Beirut,
> Bucharest, Istanbul
> Subject: Re: [Announce] Tapestry Testify project
>
> Hi Paul,
>
> Thanks for following up on this!
>
> > Next, I think my documentation is misleading you... try:
> > private static final TapestryTester SHARED_TESTER = new
> > TapestryTester("demo");
> Tried this with no luck
>
> > The documentation's example with "MyCoreModule.class" is meant to show

you

> > how to include your own "core" IOC module
> Right, and this is what I am doing, but with or without the IoC
> module I can't get it running, it fails inside TapestryTester?
>
> >First thing, the Testify sources are published to the Maven repository
> FYI I am using maven, Hmmm... I see now that there are sources in
> the repo, sorry my bad! I don't know why the sources are not being
> pulled on my side, I do use a nexus repository locally so there must
> be something going wrong there. I will try to get at the sources to
> figure out what is happening, I will let you know. Just curious if
> anyone has testify working with JUnit 4?
>
> Thanks
> Peter
>
> ----- Original Message -----
> From: "Paul Field" <paul.field@...>
> To: "Tapestry users" <users@...>
> Sent: Wednesday, 24 June, 2009 18:44:30 GMT +02:00 Athens, Beirut,
> Bucharest, Istanbul
> Subject: Re: [Announce] Tapestry Testify project
>
> P.Stavrinides@... wrote on 24/06/2009 15:35:00:
>
> > I seem to be too stupid to get testify working with JUnit 4, I can't
> > get even past the gate:
>
> I prefer to see it as a failure of my documentation :-)
>
> First thing, the Testify sources are published to the Maven repository,

so
> you can pick them up manually from:
> http://tapestry.formos.com/maven-snapshot-
> repository/com/formos/tapestry/tapestry-testify/1.0.0-SNAPSHOT/
>
> Or just ask Maven to download them for you:
> mvn [goal] -DdownloadSources=true
>
> (The m2eclipse plugin for eclipse can download them and bind them to the

> jar for you, which makes life very pleasant).
>
>
> Next, I think my documentation is misleading you... try:
>
> private static final TapestryTester SHARED_TESTER = new
> TapestryTester("demo");
>
>
> The documentation's example with "MyCoreModule.class" is meant to show

you
> how to include your own "core" IOC module
> (see:
> http://tapestry.formos.com/nightly/tapestry-testify/#Integration_testing 

> ).
>
> Alternatively, you might need to include your AppModule as the parameter
-

> if you do then read the link above about integration testing
> and break up your AppModule.
>
> Let me know how you get on!
>
> Paul
>
> ------------------
> Paul Field
> Research IT
> Deutsche Bank
>
>
>
>
> ---
>
> This e-mail may contain confidential and/or privileged information.
> If you are not the intended recipient (or have received this e-mail
> in error) please notify the sender immediately and delete this e-
> mail. Any unauthorized copying, disclosure or distribution of the
> material in this e-mail is strictly forbidden.
>
> Please refer to http://www.db.com/en/content/eu_disclosures.htm for
> additional EU corporate and regulatory disclosures.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@...
> For additional commands, e-mail: users-help@...
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@...
> For additional commands, e-mail: users-help@...
>

---

This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and delete this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.

Please refer to http://www.db.com/en/content/eu_disclosures.htm for additional EU corporate and regulatory disclosures.

[P.Stavrinides]

> So, you need to add a dependency on the tapestry-test module  (and I need
> to check what's going on in the Testify POM because you should've got that
> automatically... ).
Thanks Paul, up and running now! please keep me posted once you have the pom sorted.

Cheers
Peter

>Testify POM because you should've got that
automatically... )
----- Original Message -----
From: "Paul Field" <paul.field@...>
To: "Tapestry users" <users@...>
Sent: Thursday, 25 June, 2009 16:36:07 GMT +02:00 Athens, Beirut, Bucharest, Istanbul
Subject: Re: [Announce] Tapestry Testify project

Hi Peter,

> This is the cause:
> java.lang.ClassNotFoundException: org.apache.tapestry5.test.
> TapestryTestConstants
>
> What is TapestryTestConstants its not packaged with the jars? so I
> don't see how this can possibly work.

TapestryTestConstants is an object from org.apache.tapestry5.test:
http://tapestry.apache.org/tapestry5/apidocs/org/apache/tapestry5/test/TapestryTestConstants.html

So, you need to add a dependency on the tapestry-test module  (and I need
to check what's going on in the Testify POM because you should've got that
automatically... ).

This is the Maven dependency I suggest, as you probably don't want the
Selenium dependencies:

<dependency>
        <groupId>org.apache.tapestry</groupId>
        <artifactId>tapestry-test</artifactId>
        <version>${tapestry.version}</version>
        <scope>test</scope>
        <exclusions>
                <exclusion>
                        <groupId>org.openqa.selenium.client-drivers</
groupId>
                        <artifactId>selenium-java-client-driver</
artifactId>
                </exclusion>
                <exclusion>
                        <groupId>org.openqa.selenium.server</groupId>
                        <artifactId>selenium-server</artifactId>
                </exclusion>
                <exclusion>
                        <groupId>org.openqa.selenium.server</groupId>
                        <artifactId>selenium-server-coreless</artifactId>
                </exclusion>
        </exclusions>
</dependency>

FYI, I'm not convinced that you should have to have this dependency at
all. See:
https://issues.apache.org/jira/browse/TAP5-758

Paul
------------------
Paul Field
Research IT
Deutsche Bank

>
> Kind regards,
> Peter
>
> ----- Original Message -----
> From: "P Stavrinides" <P.Stavrinides@...>
> To: "Tapestry users" <users@...>
> Sent: Thursday, 25 June, 2009 10:38:32 GMT +02:00 Athens, Beirut,
> Bucharest, Istanbul
> Subject: Re: [Announce] Tapestry Testify project
>
> Hi Paul,
>
> Thanks for following up on this!
>
> > Next, I think my documentation is misleading you... try:
> > private static final TapestryTester SHARED_TESTER = new
> > TapestryTester("demo");
> Tried this with no luck
>
> > The documentation's example with "MyCoreModule.class" is meant to show

you

> > how to include your own "core" IOC module
> Right, and this is what I am doing, but with or without the IoC
> module I can't get it running, it fails inside TapestryTester?
>
> >First thing, the Testify sources are published to the Maven repository
> FYI I am using maven, Hmmm... I see now that there are sources in
> the repo, sorry my bad! I don't know why the sources are not being
> pulled on my side, I do use a nexus repository locally so there must
> be something going wrong there. I will try to get at the sources to
> figure out what is happening, I will let you know. Just curious if
> anyone has testify working with JUnit 4?
>
> Thanks
> Peter
>
> ----- Original Message -----
> From: "Paul Field" <paul.field@...>
> To: "Tapestry users" <users@...>
> Sent: Wednesday, 24 June, 2009 18:44:30 GMT +02:00 Athens, Beirut,
> Bucharest, Istanbul
> Subject: Re: [Announce] Tapestry Testify project
>
> P.Stavrinides@... wrote on 24/06/2009 15:35:00:
>
> > I seem to be too stupid to get testify working with JUnit 4, I can't
> > get even past the gate:
>
> I prefer to see it as a failure of my documentation :-)
>
> First thing, the Testify sources are published to the Maven repository,

so
> you can pick them up manually from:
> http://tapestry.formos.com/maven-snapshot-
> repository/com/formos/tapestry/tapestry-testify/1.0.0-SNAPSHOT/
>
> Or just ask Maven to download them for you:
> mvn [goal] -DdownloadSources=true
>
> (The m2eclipse plugin for eclipse can download them and bind them to the

> jar for you, which makes life very pleasant).
>
>
> Next, I think my documentation is misleading you... try:
>
> private static final TapestryTester SHARED_TESTER = new
> TapestryTester("demo");
>
>
> The documentation's example with "MyCoreModule.class" is meant to show

you
> how to include your own "core" IOC module
> (see:
> http://tapestry.formos.com/nightly/tapestry-testify/#Integration_testing 

> ).
>
> Alternatively, you might need to include your AppModule as the parameter
-

> if you do then read the link above about integration testing
> and break up your AppModule.
>
> Let me know how you get on!
>
> Paul
>
> ------------------
> Paul Field
> Research IT
> Deutsche Bank
>
>
>
>
> ---
>
> This e-mail may contain confidential and/or privileged information.
> If you are not the intended recipient (or have received this e-mail
> in error) please notify the sender immediately and delete this e-
> mail. Any unauthorized copying, disclosure or distribution of the
> material in this e-mail is strictly forbidden.
>
> Please refer to http://www.db.com/en/content/eu_disclosures.htm for
> additional EU corporate and regulatory disclosures.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@...
> For additional commands, e-mail: users-help@...
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@...
> For additional commands, e-mail: users-help@...
>

---

This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and delete this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.

Please refer to http://www.db.com/en/content/eu_disclosures.htm for additional EU corporate and regulatory disclosures.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[Paul Field-4]

> > So, you need to add a dependency on the tapestry-test module  (and I
need
> > to check what's going on in the Testify POM because you should've got
that
> > automatically... ).

> Thanks Paul, up and running now! please keep me posted once you have
> the pom sorted.

The latest snapshot's POM should pull in tapestry-test for you
transitively.

I've also made a change so that the Testify module doesn't get
automatically picked up by Tapestry - so this should prevent it wiring
itself into a running application by accident. This should be a
backward-compatible change that should make no difference to your tests.
But if it does let me know :-)

Paul



---

This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and delete this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.

Please refer to http://www.db.com/en/content/eu_disclosures.htm for additional EU corporate and regulatory disclosures.

[P.Stavrinides]

> The latest snapshot's POM should pull in tapestry-test for you
> transitively.
>The latest snapshot's POM should pull in tapestry-test for you
>transitively.
Great stuff, it seems to work, thanks Paul!


----- Original Message -----
From: "Paul Field" <paul.field@...>
To: "Tapestry users" <users@...>
Sent: Tuesday, 30 June, 2009 12:54:56 GMT +02:00 Athens, Beirut, Bucharest, Istanbul
Subject: Re: [Announce] Tapestry Testify project

> > So, you need to add a dependency on the tapestry-test module  (and I
need
> > to check what's going on in the Testify POM because you should've got
that
> > automatically... ).

> Thanks Paul, up and running now! please keep me posted once you have
> the pom sorted.

The latest snapshot's POM should pull in tapestry-test for you
transitively.

I've also made a change so that the Testify module doesn't get
automatically picked up by Tapestry - so this should prevent it wiring
itself into a running application by accident. This should be a
backward-compatible change that should make no difference to your tests.
But if it does let me know :-)

Paul



---

This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and delete this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.

Please refer to http://www.db.com/en/content/eu_disclosures.htm for additional EU corporate and regulatory disclosures.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[P.Stavrinides]

Hi Paul,

I hope you won't mind if I pick your brain a little more. I may be having an issue again with transitive dependencies.

I have now written a suite of tests using JUnit 4, Mockito (thanks for this tip! ...VERY happy with it) and Testify, it all works great in eclipse but the tests won't run from the command line using mvn test (surefire plugin).

I suspect that Testify is sourcing in JUnit 3.8.1 and TestNG and trying to run my tests with those, and as I have no reference to either in my project I am guessing they come fro Testify... take a look at this debug output:

[INFO] [surefire:test]
[DEBUG] dummy:dummy:jar:1.0 (selected for null)
[DEBUG]   org.apache.maven.surefire:surefire-booter:jar:2.4.3:runtime (selected for runtime)
[DEBUG]     org.apache.maven.surefire:surefire-api:jar:2.4.3:runtime (selected for runtime)
[DEBUG] Adding to surefire booter test classpath: /home/pstavrin/.m2/repository/org/apache/maven/surefire/surefire-booter/2.4.3/surefire-booter-2.4.3.jar
[DEBUG] Adding to surefire booter test classpath: /home/pstavrin/.m2/repository/org/apache/maven/surefire/surefire-api/2.4.3/surefire-api-2.4.3.jar
[DEBUG] dummy:dummy:jar:1.0 (selected for null)
[DEBUG]   org.testng:testng:jar:jdk15:5.8:test (selected for test)
[DEBUG]     junit:junit:jar:3.8.1:test (selected for test)
[DEBUG] Adding to surefire booter test classpath: /home/pstavrin/.m2/repository/org/testng/testng/5.8/testng-5.8-jdk15.jar
[DEBUG] Adding to surefire booter test classpath: /home/pstavrin/.m2/repository/junit/junit/3.8.1/junit-3.8.1.jar
[DEBUG] dummy:dummy:jar:1.0 (selected for null)
[DEBUG] Retrieving parent-POM: org.apache.maven.surefire:surefire-providers::2.4.3 for project: null:surefire-testng:jar:null from the repository.
[DEBUG] Adding managed dependencies for unknown:surefire-testng
[DEBUG]   org.apache.maven.surefire:surefire-api:jar:2.4.3
[DEBUG]   org.apache.maven.surefire:surefire-booter:jar:2.4.3
[DEBUG]   org.codehaus.plexus:plexus-utils:jar:1.5.1
[DEBUG]   org.apache.maven.surefire:surefire-testng:jar:2.4.3:test (selected for test)
[DEBUG]     junit:junit:jar:3.8.1:test (selected for test)
[DEBUG]     org.apache.maven.surefire:surefire-api:jar:2.4.3:test (selected for test)
[DEBUG]     org.apache.maven:maven-artifact:jar:2.0:test (selected for test)
[DEBUG]       org.codehaus.plexus:plexus-utils:jar:1.0.4:test (selected for test)
[DEBUG]     org.testng:testng:jar:jdk15:5.7:test (selected for test)
[DEBUG] Adding to surefire test classpath: /home/pstavrin/.m2/repository/org/apache/maven/surefire/surefire-testng/2.4.3/surefire-testng-2.4.3.jar
[DEBUG] Adding to surefire test classpath: /home/pstavrin/.m2/repository/junit/junit/3.8.1/junit-3.8.1.jar
[DEBUG] Adding to surefire test classpath: /home/pstavrin/.m2/repository/org/apache/maven/surefire/surefire-api/2.4.3/surefire-api-2.4.3.jar
[DEBUG] Adding to surefire test classpath: /home/pstavrin/.m2/repository/org/apache/maven/maven-artifact/2.0/maven-artifact-2.0.jar
[DEBUG] Adding to surefire test classpath: /home/pstavrin/.m2/repository/org/codehaus/plexus/plexus-utils/1.0.4/plexus-utils-1.0.4.jar
[DEBUG] Test Classpath :

Needless to say none of the tests will run as a result. How can I fix this, any idea?

Thanks again for your help.

Peter







----- Original Message -----
From: "P Stavrinides" <P.Stavrinides@...>
To: "Tapestry users" <users@...>
Sent: Tuesday, 30 June, 2009 13:00:37 GMT +02:00 Athens, Beirut, Bucharest, Istanbul
Subject: Re: [Announce] Tapestry Testify project


> The latest snapshot's POM should pull in tapestry-test for you
> transitively.
>The latest snapshot's POM should pull in tapestry-test for you
>transitively.
Great stuff, it seems to work, thanks Paul!


----- Original Message -----
From: "Paul Field" <paul.field@...>
To: "Tapestry users" <users@...>
Sent: Tuesday, 30 June, 2009 12:54:56 GMT +02:00 Athens, Beirut, Bucharest, Istanbul
Subject: Re: [Announce] Tapestry Testify project

> > So, you need to add a dependency on the tapestry-test module  (and I
need
> > to check what's going on in the Testify POM because you should've got
that
> > automatically... ).

> Thanks Paul, up and running now! please keep me posted once you have
> the pom sorted.

The latest snapshot's POM should pull in tapestry-test for you
transitively.

I've also made a change so that the Testify module doesn't get
automatically picked up by Tapestry - so this should prevent it wiring
itself into a running application by accident. This should be a
backward-compatible change that should make no difference to your tests.
But if it does let me know :-)

Paul



---

This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and delete this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.

Please refer to http://www.db.com/en/content/eu_disclosures.htm for additional EU corporate and regulatory disclosures.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[Paul Field-4]

Hi Peter,

 
> I suspect that Testify is sourcing in JUnit 3.8.1 and TestNG and
> trying to run my tests with those, and as I have no reference to
> either in my project I am guessing they come fro Testify... take a
> look at this debug output:

You might find it useful to use the Maven "dependency:tree" goal which
will show you all your projects dependencies and the transitive
dependencies.

I can't see that Testify would cause TestNG or JUnit to be pulled into
your project (I'm prepared to be wrong though :-) ).

I know Surefire does some interesting things around picking how to run the
tests. Have you got an explicit JUnit 4 depenency in your pom? Also make
sure you aren't using any TestNG specific things in your Surefire config
(such as suiteXmlFiles).

Other than that, if you could post the results of the dependency:tree
goal, that might help.

-- Paul



---

This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and delete this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.

Please refer to http://www.db.com/en/content/eu_disclosures.htm for additional EU corporate and regulatory disclosures.

[P.Stavrinides]

Hi Paul,

Thanks for the reply!

>I know Surefire does some interesting things around picking how to run the
>tests. Have you got an explicit JUnit 4 depenency in your pom? Also make
>sure you aren't using any TestNG specific things in your Surefire config
>(such as suiteXmlFiles).
Yes, JUnit 4.1, and I don't use TestNG, so I have no explicit reference to the plugin in my POM.

>Other than that, if you could post the results of the dependency:tree
>goal, that might help.
Okay, here is my tree:

[INFO] [dependency:tree]
[INFO] com.albourne.web:webframework:jar:5.11-SNAPSHOT
[INFO] +- com.formos.tapestry:tapestry-testify:jar:1.0.0-SNAPSHOT:test
[INFO] |  \- org.apache.tapestry:tapestry-test:jar:5.1.0.5:test
[INFO] |     \- org.testng:testng:jar:jdk15:5.8:test
[INFO] +- HFDB:hfdb:jar:5.11-SNAPSHOT:compile
[INFO] |  +- commons:commons-httpclient:jar:2.0.2:compile
[INFO] |  +- db4o:db4o-java5:jar:6.1.604:compile
[INFO] |  +- editlivejava:editlivejava:jar:6.5.4.29:compile
[INFO] |  \- HFDB:hfdb-widgets:jar:5.11-SNAPSHOT:compile
[INFO] |     +- jgoodies:forms:jar:1.2.1:compile
[INFO] |     +- jgoodies:looks:jar:2.2.0:compile
[INFO] |     +- jxlayer:jxlayer:jar:3.0:compile
[INFO] |     +- HFDB:hfdb-report:jar:5.11-SNAPSHOT:compile
[INFO] |     |  \- HFDB:hfdb-model:jar:5.11-SNAPSHOT:compile
[INFO] |     |     +- jxl:jxl:jar:2.6.8.4:compile
[INFO] |     |     +- swingx:swingx:jar:2007.9.16:compile
[INFO] |     |     +- antlr:antlr:jar:2.7.7:compile
[INFO] |     |     +- stringtemplate:stringtemplate:jar:3.2:compile
[INFO] |     |     \- HFDB:hfdb-db:jar:5.11-SNAPSHOT:compile
[INFO] |     |        +- commons:commons-dbcp:jar:1.2.2:compile
[INFO] |     |        +- commons:commons-pool:jar:1.3:compile
[INFO] |     |        +- jcommon:jcommon:jar:1.0.12:compile
[INFO] |     |        +- jfreechart:jfreechart:jar:1.0.11:compile
[INFO] |     |        +- postgresql:postgresql-jdbc2:jar:8.3.603:compile
[INFO] |     |        +- xmlrpc:xmlrpc:jar:1.1:compile
[INFO] |     |        +- xmlrpc:simple:jar:4.0.1:compile
[INFO] |     |        +- xmlrpc:simple-xmlrpc:jar:1.0:compile
[INFO] |     |        \- HFDB:hfdb-utils:jar:5.11-SNAPSHOT:compile
[INFO] |     |           +- commons-io:commons-io:jar:1.3:compile
[INFO] |     |           +- commons-lang:commons-lang:jar:2.3:compile
[INFO] |     |           +- ipworks:ipworks:jar:8.0.3383:compile
[INFO] |     |           +- apache:apache-mime4j:jar:0.3.1:compile
[INFO] |     |           +- jama:jama:jar:1.0.2:compile
[INFO] |     |           +- bouncycastle:bcprov:jar:1.40:compile
[INFO] |     |           +- bouncycastle:bcmail:jar:1.40:compile
[INFO] |     |           +- itext:itext-hyph-xml:jar:1.0:compile
[INFO] |     |           +- itext:itext:jar:2.1.3.p:compile
[INFO] |     |           +- tidy:tidy:jar:1.0:compile
[INFO] |     |           +- jgoodies:binding:jar:2.0.6:compile
[INFO] |     |           +- jgoodies:validation:jar:2.0.1:compile
[INFO] |     |           +- mailapi:mailapi:jar:1.4:compile
[INFO] |     |           +- jutf7:jutf7:jar:1.0.0:compile
[INFO] |     |           +- commons-logging:commons-logging:jar:1.0.4:compile
[INFO] |     |           \- HFDB:hfdb-properties:jar:5.11-SNAPSHOT:compile
[INFO] |     \- HFDB:hfdb-resources:jar:5.11-SNAPSHOT:compile
[INFO] +- org.apache.tapestry:tapestry-core:jar:5.1.0.5:compile
[INFO] |  +- org.apache.tapestry:tapestry-ioc:jar:5.1.0.5:compile
[INFO] |  |  +- org.apache.tapestry:tapestry5-annotations:jar:5.1.0.5:compile
[INFO] |  |  +- javassist:javassist:jar:3.9.0.GA:compile
[INFO] |  |  +- org.slf4j:slf4j-api:jar:1.5.2:compile
[INFO] |  |  \- org.slf4j:slf4j-log4j12:jar:1.5.2:compile
[INFO] |  +- commons-codec:commons-codec:jar:1.3:compile
[INFO] |  +- org.antlr:antlr-runtime:jar:3.1.1:compile
[INFO] |  \- org.codehaus.woodstox:woodstox-core-asl:jar:4.0.3:compile
[INFO] |     +- stax:stax-api:jar:1.0.1:compile
[INFO] |     \- org.codehaus.woodstox:stax2-api:jar:3.0.1:compile
[INFO] +- log4j:log4j:jar:1.2.14:compile
[INFO] +- junit:junit:jar:4.1:compile
[INFO] +- org.mockito:mockito-all:jar:1.8.0-rc2:compile
[INFO] +- easymock:easymock2:jar:2.4:test
[INFO] +- javax.servlet:servlet-api:jar:2.5:compile
[INFO] +- org.directwebremoting:dwr:jar:3.0rc1:compile
[INFO] \- javax.mail:mail:jar:1.4.1:compile
[INFO]    \- javax.activation:activation:jar:1.1:compile

Kind regards,
Peter

----- Original Message -----
From: "Paul Field" <paul.field@...>
To: "Tapestry users" <users@...>
Cc: "Tapestry users" <users@...>
Sent: Thursday, 9 July, 2009 16:10:11 GMT +02:00 Athens, Beirut, Bucharest, Istanbul
Subject: Re: [Announce] Tapestry Testify project

Hi Peter,

 
> I suspect that Testify is sourcing in JUnit 3.8.1 and TestNG and
> trying to run my tests with those, and as I have no reference to
> either in my project I am guessing they come fro Testify... take a
> look at this debug output:

You might find it useful to use the Maven "dependency:tree" goal which
will show you all your projects dependencies and the transitive
dependencies.

I can't see that Testify would cause TestNG or JUnit to be pulled into
your project (I'm prepared to be wrong though :-) ).

I know Surefire does some interesting things around picking how to run the
tests. Have you got an explicit JUnit 4 depenency in your pom? Also make
sure you aren't using any TestNG specific things in your Surefire config
(such as suiteXmlFiles).

Other than that, if you could post the results of the dependency:tree
goal, that might help.

-- Paul



---

This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and delete this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.

Please refer to http://www.db.com/en/content/eu_disclosures.htm for additional EU corporate and regulatory disclosures.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[Paul Field-4]

Hi Peter,

> Okay, here is my tree:
>
> [INFO] [dependency:tree]
> [INFO] com.albourne.web:webframework:jar:5.11-SNAPSHOT
> [INFO] +- com.formos.tapestry:tapestry-testify:jar:1.0.0-SNAPSHOT:test
> [INFO] |  \- org.apache.tapestry:tapestry-test:jar:5.1.0.5:test
> [INFO] |     \- org.testng:testng:jar:jdk15:5.8:test
> [INFO] +- HFDB:hfdb:jar:5.11-SNAPSHOT:compile

Aha! So, Testify is bringing in tapestry-test and that's bringing in
TestNG. Hmmm.... didn't see that in my own project's tree for some reason.

Anyway, I suggest that to work round the problem, you add an exclusion to
the Testify dependency; something like this:

<dependency>
  <groupId>com.formos.tapestry</groupId>
  <artifactId>tapestry-testify</artifactId>
  <version>1.0.0-SNAPSHOT</version>
  <scope>test</scope>
  <exclusions>
    <exclusion>
      <groupId>org.testng</groupId>
      <artifactId>testng</artifactId>
    </exclusion>
  </exclusions>
</dependency>

And in the next few days, I will update the Testify POM to have that
exclusion in it.

-- Paul

>
> ----- Original Message -----
> From: "Paul Field" <paul.field@...>
> To: "Tapestry users" <users@...>
> Cc: "Tapestry users" <users@...>
> Sent: Thursday, 9 July, 2009 16:10:11 GMT +02:00 Athens, Beirut,
> Bucharest, Istanbul
> Subject: Re: [Announce] Tapestry Testify project
>
> Hi Peter,
>
>
> > I suspect that Testify is sourcing in JUnit 3.8.1 and TestNG and
> > trying to run my tests with those, and as I have no reference to
> > either in my project I am guessing they come fro Testify... take a
> > look at this debug output:
>
> You might find it useful to use the Maven "dependency:tree" goal which
> will show you all your projects dependencies and the transitive
> dependencies.
>
> I can't see that Testify would cause TestNG or JUnit to be pulled into
> your project (I'm prepared to be wrong though :-) ).
>
> I know Surefire does some interesting things around picking how to run

the
> tests. Have you got an explicit JUnit 4 depenency in your pom? Also make

> sure you aren't using any TestNG specific things in your Surefire config

> (such as suiteXmlFiles).
>
> Other than that, if you could post the results of the dependency:tree
> goal, that might help.
>
> -- Paul
>
>
>
> ---
>
> This e-mail may contain confidential and/or privileged information.
> If you are not the intended recipient (or have received this e-mail
> in error) please notify the sender immediately and delete this e-
> mail. Any unauthorized copying, disclosure or distribution of the
> material in this e-mail is strictly forbidden.
>
> Please refer to http://www.db.com/en/content/eu_disclosures.htm for
> additional EU corporate and regulatory disclosures.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@...
> For additional commands, e-mail: users-help@...
>

---

This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and delete this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.

Please refer to http://www.db.com/en/content/eu_disclosures.htm for additional EU corporate and regulatory disclosures.