[
http://jira.codehaus.org/browse/SUREFIRE-498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Gruber updated SUREFIRE-498:
--------------------------------------
Attachment: fixture.diff
This is a better diff, which is applied not to surefire-api but to the root of
the surefire tree. It adds more explicit criteria for looking up the fixture
methods, and also adds some documentation for pojo tests which includes
explicitly naming the methods to implement for fixture.
> POJO tests have only partially implemented fixture support
> ----------------------------------------------------------
>
> Key: SUREFIRE-498
> URL: http://jira.codehaus.org/browse/SUREFIRE-498
> Project: Maven Surefire
> Issue Type: Bug
> Reporter: Christian Gruber
> Attachments: fixture.diff, fixture.diff
>
>
> The current support for POJO executes each test method, and before and after
> each test method there is a method on PojoTestSet executed for fixture setup
> and teardown. In the executeMethod() method, there are try/catch blocks
> around a delegated method (setUpFixture() and tearDownFixture()) but the
> implementation of those two methods is empty. So under no circumstances is
> setup or teardown able to occur, except with in each method.
> I've attached a patch which looks up the setUp() and tearDown() public
> methods on the pojo test class, and if such exist, executes them
> appropriately. All the try/catch logic is already there - it just needed the
> last step of deciding what these methods were going to be called, and calling
> them.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
