You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "Christian E Gruber (JIRA)" <ji...@apache.org> on 2010/06/09 01:03:11 UTC

[jira] Updated: (TAP5-1183) Factor out TestUtils methods that aren't assertion-related so they can be used wihout requiring TestNG in teh classpath.

     [ https://issues.apache.org/jira/browse/TAP5-1183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Christian E Gruber updated TAP5-1183:
-------------------------------------

    Attachment: extract-property-utils.patch

Patch attached which pulls out a PropertyUtils class with the appropriate methods for handling components with @Property syntax, and keeps some methods with equivalent signatures in TestUtil in order to preserve the type hierarchy and shape for backward compatibility.

> Factor out TestUtils methods that aren't assertion-related so they can be used wihout requiring TestNG in teh classpath.
> ------------------------------------------------------------------------------------------------------------------------
>
>                 Key: TAP5-1183
>                 URL: https://issues.apache.org/jira/browse/TAP5-1183
>             Project: Tapestry 5
>          Issue Type: Improvement
>          Components: tapestry-ioc
>    Affects Versions: 5.2
>            Reporter: Christian E Gruber
>         Attachments: extract-property-utils.patch
>
>
> TestUtils provides two classes of functionality - one which provides additional Assertions, and other which provides methods for handling components containing @Property annotations.
> TestUtils forms the base class for TestBase, in order to conveniently provide access to the assertion methods, and to that end also inherits org.testng.Assert.  The second class of functionality is valuable regardless of your testing framework, but requires that TestNG be in the classpath to satisfy the structural dependency.  It would be preferable for these three (plus one private) methods to be pulled out of TestUtils into another class, perhaps with delegating methods retained for backwards compatibility.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.