[jbossts-issues] [JBoss JIRA] (JBTM-1804) JTS remote tests not run and no code coverage

Tom Jenkinson (JIRA) jira-events at lists.jboss.org
Wed Jun 26 07:23:21 EDT 2013


     [ https://issues.jboss.org/browse/JBTM-1804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tom Jenkinson reassigned JBTM-1804:
-----------------------------------

    Assignee: Amos Feng  (was: Tom Jenkinson)


I am assigning this to you, Amos. As Mark says the tests need converting to Junit. I would suspect that running the clients and servers in the same VM would not be a problem for the test. However, please keep the source for the tests as close to the originals as possible to ensure the tests remain accurate.

In terms of the requirements around code code coverage, the ArjunaJTS/jts/pom.xml exclude of **/remote/** is the thing that you would remove from the codeCoverage profile so that these new junit tests would then be run under emma. As this profile already instruments the main library, simply executing the test will ensure we get coverage numbers effected by this test.
                
> JTS remote tests not run and no code coverage
> ---------------------------------------------
>
>                 Key: JBTM-1804
>                 URL: https://issues.jboss.org/browse/JBTM-1804
>             Project: JBoss Transaction Manager
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: JTS, Testing
>    Affects Versions: 5.0.0.M3
>            Reporter: Mark Little
>            Assignee: Amos Feng
>
> The tests in .remote. package for JTS are not run by default. We should consider adding a build option so that they are run (will require some mods to the tests since many of them are client/server based - see associated Readme.txt files); don't run them by default since they will add delay to a normal build.
> It would then be beneficial to have them instrumented by emma to get code coverage.

--
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


More information about the jbossts-issues mailing list