Hi Mats,
I have checked your configuration and it looks correct, I am using JUnit4 and
have it working with this same setup... one thing to be conscious of is using
the correct service scope... you are aware that you may not be using
TestifyConstants.PERTEST if you source in from AppModule?
regards,
Peter
----- Original Message -----
From: "Paul Field" <paul.fi...@db.com>
To: "Tapestry users" <users@tapestry.apache.org>
Sent: Thursday, 3 September, 2009 14:54:55 GMT +02:00 Athens, Beirut,
Bucharest, Istanbul
Subject: Re: Can't get Testify & JUnit 4 & Mockito working
Mats Henricson <m...@henricson.se> wrote on 03/09/2009 12:28:23:
> My current guess is that @ForComponents is pulling in and handling
> binding from my real AppManager, even though it is in no way part
> of the test.
In that case try creating the TapestryTester with a nonsense app name:
private static final TapestryTester SHARED_TESTER
= new TapestryTester("nonsense", MyModule.class);
That will make sure Tapestry/Testify are using only the modules you
specify in the constructor.
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-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
