Hi, > ApplicationContext.recordActions( "addEmployeeTestCase1Script.txt" ); > > And Pivot would automatically record all actions made by every Component and > simulate it by > > ApplicationContext.startActions( "addEmployeeTestCase1Script.txt" ); > > this way almost nothing would invalidate the "screen based test" (I'd like > to call it "actual usage test" :D).
And so why not think at a new, dedicated subclass of ApplicationContext, specific for Tests (started by JUnit or maybe standard executions) ... Comments / ideas ? > Right now I'm trying to use Spring in my app, any advice? (my app is just a > simple data-centric/crud w/ pivot ui-app) I used Spring (but not too much :-( ), and without JPA, sorry ... For some webapps in last months I'm rethinking all the infrastructure, so instead of plain java (and classic frameworks) I'm starting to evaluating Groovy and Scala (and Jython for some things), with great web frameworks like Grails (it uses Spring and Hibernate, but hiding them as much as possible !!) ... maybe there you can find some inspiration ... In any case I'd suggest you to avoid direct usage from Clients of Server Objects (if not only for Domain Objects), and rely only of JSON or XML data exchange, and have that data converted to Domain Objects (shared between server and client code ... in ejb terms this is part of ejb client). Uh, sorry in your application the data is on server, right ? Because if you have direct access to data (the data is on the client) probably my previous point could not apply (too much) ... Bye, Sandro
