A passion, technology.
Imagine a working environment which promotes technological innovation and curiosity.
Imagine a group where you will have opportunity to work and to share with people among the most gifted.
Imagine a culture and stocks in break with SSII.
Imagine a society where your talents and your ideas will be admitted and encouraged.
Imagine an organisation which gives you the medium reals to work, to advance, to accomplish your personal plans.
Do not imagine any more, live him!
Do not hesitate to contact us across the Form of contact or directly at address recrutement@xebia.fr.
ADDM Adobe Android annotation GAPED development Devoxx Eclipse ESB WORKING FLASH FLEX GOOGLE GROOVY GWT HIBERNATE IBM J2EE POPULAR DANCE JAVAFX JAZOON JBOSS jdk-7 scala SCRUM SOA JEE JPA JSF JVM agile Methods MAVEN ORACLE OSGI PARIS JUG PERFORMANCE RIA SPRING SPRINGSOURCE SUN TOMCAT WEBSPHERE WICKET XEBIA XP
is a brain tumour, exclusively devoted to technologies J2EE.
Except opposite mention, the contents of this blog are under .
Among the inevitable tasks of the life of a developer, there is the writing of the unit tests. Many tools try to make life easier for us on this point. Today, I am going to speak to you about JTESTR, a framework of unit tests who brings power and speed of writing of the scripting to test Popular dance applications. Thrown by Ola Bini, an inevitable contributor the plan JRUBY, JTESTR is directly integrable with Ant, and Maven 2. This plan is not still very spread, but it brings advantages which are worth being studied.
Here is the list of tickets most read on this blog in April, May and June:
XKE (Xebia Knowledge Exchange) of March was a chance to introduce the step of urbanization. Introduced example did not follow holding portray: a step of urbanization is adapted according to plans and organisations to which it is applied.
The purpose of this ticket is to unwind this step in a simplified way. It will give us the occasion to define the used vocabulary, and to make an official report on this step.
We will unwind example with an approach TOP-DOWN, that is the analysis begins with the definition of strategy to go down then through the different strata of YES. For example, we will take the case of a travel agency which buys and sells trips.
The unit tests are not that a good practice of agile methods, they are a true pre-requesting in the installation of an iterative development.
The refactoring and the modification of an existent base of code, although made easier by the current environments of development, include an obvious risk of decline, partly covered by the unit tests.
You will find in this ticket our 10 command of the unit tests.
The announcement of SpringSource has paces of schism. After years to criticise complexity and monolithic nature of Popular dance Enterprise Edition (Popular dance EE), the teams of Rod Johnson crossed Rubicon and offer a server of applications Popular dance which will not rest specification on monolithic Popular dance EE.
SpringSource Application Platform limits itself to some fragments of this specification (mainly Servlet and JPA) put together in a container OSGI augmented by some features Spring. Applications web will not be any more put together in form of WAR with a file web but in form of several BUNDLES OSGI with files of shape Spring.
Read this article
The unit tests are not that a good practice of agile methods, they are a true pre-requesting in the installation of an iterative development.
The refactoring and the modification of an existent base of code, although made easier by the current environments of development, include an obvious risk of decline, partly covered by the unit tests.
You will find below our 10 command of the unit tests.
XP DAY France on 2008
Paris, on May 5th and 6th, 2008
Agile conference on Agile methods! http://www.xpday.fr
You are in search of new ideas to make more efficient your software plans of development
You wish their borders in knowledge more on agile methods, their benefits,
You set agile practices up within your plans and you want to confront your returns of experience with those of other practitioners
There are many people of us who have already used JUNIT to write tests.
Which is the one who was not disappointed by inherent limitations in different methods assertXXX() ?
Which is the one who did not use additional bookshops (JUnit-addons, Unitils) packaging of the utilitarian methods of type assertContains, ?
What is the one who did not write his own utilitarian method?
If you feel concerned, read the continuation of this article which lands:
Xebia IT Architects lock France
Defence Colis e - 10/12, avenue of The Ark
92419 Courbevoie Cedex
T l : +33 (0) 1 46 91 76 16
Fax : +33 (0) 1 46 91 88 00
E-mail : info@xebia.fr