To consider when arquilling

After a few weeks of real world testing with Arquillian I’ve noticed a few things to consider when building integration tests. These items should grow or evolve, here or in other post, as experience is gained.

To manage provided dependencies. The building of a project most of the time considers dependencies to libraries, toolkits, frameworks, etc., and for each of them you define a scope. You find some to be provided-scoped as your company’s login jar, the jee6-spec.jar library, etc. What’s to consider here is that these libraries are provided by the environment, so they don’t need to be in your deployment file. If you just drop them in your deploy or lib folders when you start the container, without your test file yet, you can make sure the can actually deploy by them selves. Then, if your test-deployment-file fails to deploy it’s less likely because of the provided dependencies. Read the rest of this entry »

Target Entity

Lately I’ve been fighting with some teory vs practice which refused to cooperate and that’s become a bit frustrating. My problem was an API which looked OK but when time came to persist it with JPA entities it needed so much tweaking, pushing and pulling generics to get that covariant return to work that really felt something was terribly wrong. The point was to write an API which would allow the persistence layer implement it and still be manageable and targeted by the entity manager, but something wasn’t fitting.
Read the rest of this entry »

Code auditing with Maven

Every time you code and promise you’ll eliminate duplicated code later, replace System.out.println with a proper logger tomorrow, refactor that 15-options-if before the weekend you get into a debt you can’t pay. Even worst, your already big debt gets bigger. So, there are not more loans for you. Here’s a code auditing profile to be run in every build. Read the rest of this entry »

Code coverage with Maven and Cobertura

Cobertura‘s usage is covered in its page so that you can install the plugin and run it separately from the build lifecycle. This how-to integrates it with maven3 to run as part of the site lifecycle. Read the rest of this entry »

Three lessons out of spilled milk

A couple of years ago at work started a move towards MDA guided by the architecture area. Former essays delivered MVC layered applications which needed code implementation for business methods. Since we go as far as analyzing and designing and hire coding, what our code providers had to do was simpler, shorter, less error prone and cheaper. Actually a bold move. Now close to be filed under failures. Read the rest of this entry »