[jbossts-issues] [JBoss JIRA] Commented: (JBTM-543) qa tests should support driver selection

Jonathan Halliday (JIRA) jira-events at lists.jboss.org
Tue May 5 08:40:24 EDT 2009


    [ https://jira.jboss.org/jira/browse/JBTM-543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12465751#action_12465751 ] 

Jonathan Halliday commented on JBTM-543:
----------------------------------------

There are a couple of different approaches to this.

The 'DTF' style one is to define multiple classpaths in the product config file (JBossTS_JTS_JacORB_QA.xml) then have multiple node configurations, each referencing a different classpath. Finally a set of different nodeconfig.xml files, each referencing a different 'os' name i.e. node config / classpath. That's a log of extra xml as the number of db drivers grows.

The second approach is to construct a default classpath containing a generic 'dbdriver.jar' entry but no other db drivers (unlike now where all the drivers are on the classpath, although at most one version of each), then use the run-dtf-local.xml file to copy the desired driver from a holding dir to 'dbdriver.jar' for each set of tests. This becomes a pain the next when a driver has more than one .jar though. Maybe use a dir rather than a .jar, as the config is reloaded for each test group and will rescan the dir at that time anyhow.

> qa tests should support driver selection
> ----------------------------------------
>
>                 Key: JBTM-543
>                 URL: https://jira.jboss.org/jira/browse/JBTM-543
>             Project: JBoss Transaction Manager
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.6.1
>            Reporter: Jonathan Halliday
>            Assignee: Jonathan Halliday
>             Fix For: 4.7.0
>
>
> For some database servers we want to runs tests with multiple different versions of the drivers. This is non-trivial, as the driver versions each use the same classnames, so only one version can be on the classpath at a time. We'll need some kind of config mechanism to alter the classpath on the fly.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        



More information about the jbossts-issues mailing list