Paul Field wrote on 28/07/2009 09:35:05:
> rolfst wrote on 27/07/2009 14:13:51:
> > Yes there are three groups involved in the suite.
> > How ever no other test from other groups are available.
> > It seems that when I remove the reference to groups in my testng.xml
it
> > works fine.
> >
> >
rolfst wrote on 27/07/2009 14:13:51:
> Hi Paul,
>
> Yes there are three groups involved in the suite.
> How ever no other test from other groups are available.
> It seems that when I remove the reference to groups in my testng.xml it
> works fine.
>
> For now a workable solution it looks like a
_disclosures.htm for
> additional EU corporate and regulatory disclosures.
>
--
View this message in context:
http://www.nabble.com/Testify-injection-only-works-once-per-test-tp24665202p24680484.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
--
rolfst wrote on 27/07/2009 13:26:23:
>
>@Test(groups = "rbudisplay")
>public void test_rbuselection_fulltype() throws Exception
>{
Oooo... it might be something to do with groups. Is your suite specifying
that only certain groups are run?
(my brain aches whenever I try to work out
>
>
> ---
>
> 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 distr
On Jul 27, 2009, at 6:25 AM, Paul Field wrote:
If you are setting up state that you want to be fresh for each test,
then
you should consider using Testify's pertest scope:
http://tapestry.formos.com/nightly/tapestry-testify/#Per-test_scope
Ah... this is what I was thinking - thanks for poi
Christian Edward Gruber wrote on
27/07/2009 11:07:41:
> I think that @BeforeMethod is a better one to key off-of. If
> singleton-scoped objects are the only ones being injected, then
> @BeforeClass makes sense, but if you're testing per-request or per-
> session objects, then it's best to use
I think that @BeforeMethod is a better one to key off-of. If
singleton-scoped objects are the only ones being injected, then
@BeforeClass makes sense, but if you're testing per-request or per-
session objects, then it's best to use @BeforeMethod, since you may be
setting state on these whic
Hi Rolf,
> Hi I am using Testify to inject a fake repository into my testng test
but I
> come op to a problem.
>
> when i first access the fake repository it gets injected however the
second
> time i access the repository I get a null pointer exception.
>
> Now comes another strange thing whe
works fine and the
repository gets injected perfectly.
Any ideas?
Regards,
Rolf
--
View this message in context:
http://www.nabble.com/Testify-injection-only-works-once-per-test-tp24665202p24665202.html
Sent from the Tapestry - User mailing list archive at Nabble.com
10 matches
Mail list logo
