You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jena.apache.org by "Andy Seaborne (JIRA)" <ji...@apache.org> on 2013/01/15 16:32:12 UTC
[jira] [Resolved] (JENA-370) No test cases for alternative Model
implementations
[ https://issues.apache.org/jira/browse/JENA-370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andy Seaborne resolved JENA-370.
--------------------------------
Resolution: Fixed
Fix Version/s: Jena 2.10.0
Assignee: Andy Seaborne
See JENA-380 for more test work.
> No test cases for alternative Model implementations
> ---------------------------------------------------
>
> Key: JENA-370
> URL: https://issues.apache.org/jira/browse/JENA-370
> Project: Apache Jena
> Issue Type: Test
> Components: Jena
> Affects Versions: Jena 2.7.4
> Reporter: Claude Warren
> Assignee: Andy Seaborne
> Fix For: Jena 2.10.0
>
> Attachments: JENA-370-2.10.patch, JENA370-afs-1.patch, jena-370-core-2.10-attempt2.patch, jena=370-core-2.10.patch, JENA-370.patch, JENA-370.patch
>
>
> The Model tests are all hard coded to use the ModelFactory.createDefaultModel() (and similar) model constructors. This makes it impossible for alternative implementations to verify they meet the interface contracts.
> One solution is to convert the tests to use a getModel() method ala the getGraph() method used for the graph tests.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira