[ http://issues.apache.org/jira/browse/DERBY-1353?page=all ]
Kristian Waagan updated DERBY-1353:
-----------------------------------
Summary: Add mechanism to run tests in a single leg xa transaction
(was: Add mechansim to run tests in a single leg xa transaction)
Description:
A mechanism to run JUnit tests in a single leg xa transaction is needed to be
able to test the Brokered-/LogicalConnection classes without writing specific
tests for this.
Mechanism added as part of DERBY-1214.
Brief description: Set system property 'derbyTesting.xa.single'. Parsing is
handled in 'TestConfiguration'. Search for the property constant in the Derby
JUnit base classes to find the other places where it is used (basically it
affects the 'getConnection()' call).
was:
A mechansim to run tests in a single leg xa transaction is needed to be able to
test the Brokered-/LogicalConnection classes without writing specific tests for
this.
Mechanism added as part of DERBY-1214.
Brief description: Set system property 'derbyTesting.xa.single'. Parsing is
handled in 'TestConfiguration'. Search for the property constant in the Derby
JUnit base classes to find the other places where it is used (basically it
affects the 'getConnection()' call).
Fixed spelling errors...
> Add mechanism to run tests in a single leg xa transaction
> ---------------------------------------------------------
>
> Key: DERBY-1353
> URL: http://issues.apache.org/jira/browse/DERBY-1353
> Project: Derby
> Type: Sub-task
> Components: Test
> Versions: 10.2.0.0
> Reporter: Kristian Waagan
> Assignee: Anurag Shekhar
> Priority: Minor
> Fix For: 10.2.0.0
>
> A mechanism to run JUnit tests in a single leg xa transaction is needed to be
> able to test the Brokered-/LogicalConnection classes without writing specific
> tests for this.
> Mechanism added as part of DERBY-1214.
> Brief description: Set system property 'derbyTesting.xa.single'. Parsing is
> handled in 'TestConfiguration'. Search for the property constant in the Derby
> JUnit base classes to find the other places where it is used (basically it
> affects the 'getConnection()' call).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
