Add Section on the Full Integration Tests

[ALRubinger]

Likely to be looped somewhere into "Assembly and Deployment" Chapter.

[ALRubinger]

First assigning to @aslakknutsen for outline.

[aslakknutsen]

Wondering if this needs to go under "Building and Testing GeekSeek" in Chapter 5 as well..

As the profiles will influence the user.

(Chapter 5 in output, Chapter 4 in source ;)

[aslakknutsen]

• TestSuite pr Module split in 3
  • Indication of level of testing
  • Unit
    • 'pure' unit, outside of the Container type test. Business logic unrelated to frameworks
  • Integration
    • tests that require a Container in some form.
    • CDI; EJB; REST; JPA, Infinispan, Neo4j, Transactions
  • Functional
    • tests that require external services outside of our own control
    • Twitter Security
  • Unit/Integration/Functional are split in separate maven profiles
    • Unit only executes Unit tests
    • Integration executes Unit and Integration
    • Functional execute Unit, Integration and Functional
    • Integration is default level to allow for test execution without relying on external services(with security keys etc)
    • Split to allow for a speed up for a minimal sanity check during dev
  • Story tests
    • *Story tests can be integration or functional depending on execution context
    • REST Story tests are tests that are separated from it's target deployment
    • This allows it to run on a Module level (e.g. web/rest/conference) and be included on a functional level (application)
    • In one scenario it runs against the module in isolation from the world, in the other it runs against the full final deployment