                                                                                                                                                                                                                                                                
Date: Thu, 23 Feb 2012 13:36:14 -0800 (PST)
From: Jeroen van Erp <ajvan...@gmail.com>
To: testng-users@googlegroups.com
Message-ID: <11080334.7499.1330032974251.JavaMail.geo-discussion-forums@vbai14>
Subject: Assume NG
MIME-Version: 1.0
Content-Type: multipart/mixed; 
	boundary="----=_Part_7497_23129911.1330032974250"

------=_Part_7497_23129911.1330032974250
Content-Type: multipart/alternative; 
	boundary="----=_Part_7498_16325678.1330032974250"

------=_Part_7498_16325678.1330032974250
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

Cedric, Folks,

In an attempt to get a similar behavior to JUnit's Assume.assumeThat, I've 
created "Assume NG"[1]. Using assumption annotations it is possible to 
conditionally skip certain methods, which is especially useful in @Factory 
and @DataProvider generated test(suites).

Design Rationale:
I've hooked into the IInvokedMedhodListener to check whether the method is 
annotated and check the assumptions for the test. In order to optionally 
skip the test however, I need(ed) to do a classpath override on the 
org.testng.internal.Invoker. This means that assumeng needs to go on the 
classpath before TestNG. I've looked at using IHookable instead, but then 
the test didn't register as skipped, which I think looks nicer than it not 
showing up at all.

I'm curious as to what you think, how it can be improved, and whether this 
makes for a nice addition to TestNG.

Best regards,

Jeroen van Erp
http://www.github.com/hierynomus

[1] Source at: http://www.github.com/hierynomus/assumeng

------=_Part_7498_16325678.1330032974250
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Cedric, Folks,<div><br></div><div>In an attempt to get a similar behavior t=
o JUnit's Assume.assumeThat, I've created "Assume NG"[1]. Using assumption =
annotations it is possible to conditionally skip certain methods, which is =
especially useful in @Factory and @DataProvider generated test(suites).</di=
v><div><br></div><div>Design Rationale:</div><div>I've hooked into the IInv=
okedMedhodListener to check whether the method is annotated and check the a=
ssumptions for the test. In order to optionally skip the test however, I ne=
ed(ed) to do a classpath override on the org.testng.internal.Invoker. This =
means that assumeng needs to go on the classpath before TestNG. I've looked=
 at using IHookable instead, but then the test didn't register as skipped, =
which I think looks nicer than it not showing up at all.</div><div><br></di=
v><div>I'm curious as to what you think, how it can be improved, and whethe=
r this makes for a nice addition to TestNG.</div><div><br></div><div>Best r=
egards,</div><div><br></div><div>Jeroen van Erp</div><div>http://www.github=
.com/hierynomus</div><div><br></div><div>[1] Source at: http://www.github.c=
om/hierynomus/assumeng</div>
------=_Part_7498_16325678.1330032974250--

------=_Part_7497_23129911.1330032974250--