Profile cover photo
Profile photo
Nicolas Labrot
52 followers
52 followers
About
Nicolas's posts

Post has attachment

Post has attachment

Post has attachment

Post has shared content
The Groovy development team just released Groovy 1.8.4 as well as the first beta of Groovy 2.0!

The big highlights of the announcements are the upcoming new features of the 2.0 line (formerly known as 1.9) being actively worked on: invoke dynamic support for faster dynamic dispatch, static type checking for early feedback of the compiler on common programming mistakes, and static compilation for performance as fast as Java.

Migration SVN =>Git : Success. Maven Integration : Success!

We met very few issues:
- The admin sys created non bare repository
- the Git "description" file was not filled


Now maybe the most important tasks : writing the workflow rules!

I just QueryDSLize my RDBMS schema. The process was smooth but it output my SQL Numeric type to Java BigDecimal. It seems not possible to override to Long.

SQL construction is now more robust and less error prone.

Post has attachment

Les outils comme Concordion (http://www.concordion.org/) permettent de décrire les scenarii des acceptance tests dans des formats de type mise en forme (HTML, Word...). A l’exécution du scenario, le code est lié et exécuté par le scenario décrit dans ces fichiers.

In fine c'est, de mon expérience, toujours le développeur qui a à sa charge la maintenance technique et fonctionnelle des scenarii. Pourquoi s’embarrasser d'un fichier source externe décrivant le scenario ?

L'idée est de créer le scenario du test au travers du code puis de le mettre en forme sous une forme lisible en utilisant des informations stockées dans le code.

TestNG permet assez facilement de décrire une succession d'étape composant un scenario. Je ne connais cependant pas d'outil permettant de traiter l'aspect description et mise en forme.

Cette approche est elle pertinente? Connaissez vous des outils répondant à ce besoin?

It's amazing how patterns naturally emerge from kaizen. But it's regrettable that well known patterns that emerge are not previously known.

Today I see a RCA (root cause analysis) retrospective where the solution to difficult merging is ... feature branching as explained by +Adam Dymitruk
Wait while more posts are being loaded