RE: [Springframework-developer] AbstractTransactionalSpringContextTests

[Keith D. <ke...@in...>]

>I don't quite understand what you want here. Can you please be more 
>specific? How would you drive this option?

Ideally I'd like to be able to test the Phonebook sample flows, or any other
flows, by extending AbstractTransactionalSpringContextTests, without being
*required* to set a transaction manager and run in the context of a TX.  In
other words, I'd like it to be configurable.  If it's not made configurable,
I'm only left with two options:
1. Scale up Phonebook (or any other flow) to work with a transactional data
source
2. Have a duplicate AbstractFlowExecutionTests hierarchy that just extends
from DependencyInjectedContextTests

Neither of these are that great IMO.  The former means I can really only
integration test flows that need TX's (yes that will probably be the
majority, but...) or I have to mock out the TX Manager.  The latter means I
duplicate flow integration test code, to extend from two different base
classes.

Keith

-----Original Message-----
From: spr...@li...
[mailto:spr...@li...] On Behalf Of
Rod Johnson
Sent: Wednesday, April 06, 2005 6:55 AM
To: spr...@li...
Subject: Re: [Springframework-developer]
AbstractTransactionalSpringContextTests

Keith

I will try to make any required enhancements today.

> - the ability to DISABLE dependency checking by object for the autowired 
> test - sometimes defaults really do make sense, why always require a set 
> method to be called for each public setter?
I've added a dependencyCheck property which you can call in a 
constructor. I've preserved the default dependency checking, which I 
think is useful.

> - the ability to turn off/on transaction management - right now 
> AbstractFlowExecutionTests is runnable only in the context of a database 
> transaction.  While this is great and all, if I want to integration test 
> flows outside of any transactional context, I'm screwed.  I can't 
> exactly subclass DependencyInjectedContextTests, as I still WANT THE 
> OPTION of being able to test flows in a transaction context - for the 
> flows that demand it.  But the current structure doesn't give me that 
> choice.
I don't quite understand what you want here. Can you please be more 
specific? How would you drive this option?

Rgds
Rod



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer