I am working on a project that is developing a webapp with a 100% Flex interface that talks through Blaze to a Java backend running on an application server. The team has already created many unit tests, but only created integration tests for the persistence module. Now we are wondering how best to integrate tests of other parts. Here are the Maven modules that we have now, I think this is a very typical design:
Server side:
1) Java domain module - these are only unit tests
2) Java persistence module (DAO) - right now it only has integration tests that speak with a live database for DAO testing, nothing really unit test here
3) Java service module - right now these are just unit tests
Client side:
4) the Flex services module, which is packaged as a SWC and talks to the Java backend - currently it has no tests at all
5) the Flex client module that implements the Flex interface on top of the Flex services module - currently it only has unit tests (we used MATE to create a loosely coupled client with no logic in the views).
These 5 modules are packaged in a WAR that can be deployed to an application server or servlet container.
Here are 4 questions that I have:
- , , persist , ? , , Flex-Services, .
- , Flex WAR. Flex -,
, ?
- Flex
(, -
, Flex)?
- WAR
, WAR?
/ !