[ 
https://issues.apache.org/jira/browse/JENA-380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13763004#comment-13763004
 ] 

Andy Seaborne commented on JENA-380:
------------------------------------

By "tag" do you mean "branch"? (not than SVN cares, git would). Tags are 
usually recording state, i.e. they are history and recording what was, whereas 
branches are changes in progress.  Tools support, like Eclipse, does use this 
distinction.

                
> Migrate core tests to junit4
> ----------------------------
>
>                 Key: JENA-380
>                 URL: https://issues.apache.org/jira/browse/JENA-380
>             Project: Apache Jena
>          Issue Type: Task
>          Components: Jena
>    Affects Versions: Jena 2.10.0
>            Reporter: Claude Warren
>            Assignee: Claude Warren
>            Priority: Minor
>
> Many of the tests for jena core are junit3 suites.  I would like to start a 
> process of migrating them to junit 4 and rework them so that when compiling 
> in the Eclipse IDE clicking on the failed test will take you to the failed 
> test while maintaining the current test names.  I would expect some test 
> names to change based upon changes in functionality.
> The goals of this change are :
> 1) Move to junit 4
> 2) Ensure that when the entire package is run as a junit test all tests 
> succeed. (i.e. valid default tests)
> 3) Continue to provide test classes that can be utilized by implementers of 
> interfaces.
> 4) Extract utility/helper code into utility/helper classes to simplify the 
> test inheritance tree.
> 5) Move the test classes into the same package name as the classes they test. 
>  Currently we have x.foo for the implementation classes and x.foo.test for 
> the test classes.
> The process would be:
> 1) build a number of sub tasks under this change to deliver smaller changes.  
> The smaller changes will be based on the package names and that can be 
> delivered incrementally.
> 2) once all tests are in junit4 perform a sweep across the test code base 
> looking for any junit 3 classes that remain.  Verify that their testing 
> functionality has been replaced by other code and remove them.
> The result will be a complete review of all the core tests and a migration to 
> junit 4 and annotated 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

Reply via email to