You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "PADMANAV (JIRA)" <ji...@apache.org> on 2008/08/18 16:53:44 UTC
[jira] Created: (JXPATH-126) utility to unit test the xpath
utility to unit test the xpath
------------------------------
Key: JXPATH-126
URL: https://issues.apache.org/jira/browse/JXPATH-126
Project: Commons JXPath
Issue Type: Improvement
Reporter: PADMANAV
Priority: Minor
After writing a xpath, the target class hierarchy might get changed. Can we have an utility, which can be invoked to make sure that an object graph created via the class hierarchy is still valid against the original xpath? This should definitly help with unit testing effort. Of course it can't take care of xpath's dependent on a field specific to one implementation of some interface. But still, for a design following good practices, it sholudn't be an issue.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (JXPATH-126) utility to unit test the xpath
Posted by "Matt Benson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JXPATH-126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matt Benson resolved JXPATH-126.
--------------------------------
Resolution: Won't Fix
A valid xpath is a valid xpath, regardless of whether a nodeset exists for that path. I would think you could create unit tests for your own specific needs, but I can't see much opportunity for something generic JXPath could provide beyond the facilities currently offered.
> utility to unit test the xpath
> ------------------------------
>
> Key: JXPATH-126
> URL: https://issues.apache.org/jira/browse/JXPATH-126
> Project: Commons JXPath
> Issue Type: Improvement
> Reporter: PADMANAV
> Priority: Minor
> Original Estimate: 72h
> Remaining Estimate: 72h
>
> After writing a xpath, the target class hierarchy might get changed. Can we have an utility, which can be invoked to make sure that an object graph created via the class hierarchy is still valid against the original xpath? This should definitly help with unit testing effort. Of course it can't take care of xpath's dependent on a field specific to one implementation of some interface. But still, for a design following good practices, it sholudn't be an issue.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.