Ce diaporama a bien été signalé.
Nous utilisons votre profil LinkedIn et vos données d’activité pour vous proposer des publicités personnalisées et pertinentes. Vous pouvez changer vos préférences de publicités à tout moment.
EclipseCon Eu 2013 - Living Documentation
EclipseCon Eu 2013 - Living Documentation
EclipseCon Eu 2013 - Living Documentation
EclipseCon Eu 2013 - Living Documentation
EclipseCon Eu 2013 - Living Documentation
EclipseCon Eu 2013 - Living Documentation
EclipseCon Eu 2013 - Living Documentation
EclipseCon Eu 2013 - Living Documentation
EclipseCon Eu 2013 - Living Documentation
EclipseCon Eu 2013 - Living Documentation
EclipseCon Eu 2013 - Living Documentation
EclipseCon Eu 2013 - Living Documentation
EclipseCon Eu 2013 - Living Documentation
EclipseCon Eu 2013 - Living Documentation
EclipseCon Eu 2013 - Living Documentation
EclipseCon Eu 2013 - Living Documentation
EclipseCon Eu 2013 - Living Documentation
EclipseCon Eu 2013 - Living Documentation
EclipseCon Eu 2013 - Living Documentation
EclipseCon Eu 2013 - Living Documentation
EclipseCon Eu 2013 - Living Documentation
EclipseCon Eu 2013 - Living Documentation
EclipseCon Eu 2013 - Living Documentation
EclipseCon Eu 2013 - Living Documentation
EclipseCon Eu 2013 - Living Documentation
EclipseCon Eu 2013 - Living Documentation
EclipseCon Eu 2013 - Living Documentation
EclipseCon Eu 2013 - Living Documentation
EclipseCon Eu 2013 - Living Documentation
EclipseCon Eu 2013 - Living Documentation
EclipseCon Eu 2013 - Living Documentation
EclipseCon Eu 2013 - Living Documentation
EclipseCon Eu 2013 - Living Documentation
EclipseCon Eu 2013 - Living Documentation
EclipseCon Eu 2013 - Living Documentation
EclipseCon Eu 2013 - Living Documentation
EclipseCon Eu 2013 - Living Documentation
EclipseCon Eu 2013 - Living Documentation
EclipseCon Eu 2013 - Living Documentation
EclipseCon Eu 2013 - Living Documentation
EclipseCon Eu 2013 - Living Documentation
EclipseCon Eu 2013 - Living Documentation
EclipseCon Eu 2013 - Living Documentation
EclipseCon Eu 2013 - Living Documentation
Prochain SlideShare
Chargement dans…5
×

sur

EclipseCon Eu 2013 - Living Documentation Slide 1 EclipseCon Eu 2013 - Living Documentation Slide 2 EclipseCon Eu 2013 - Living Documentation Slide 3 EclipseCon Eu 2013 - Living Documentation Slide 4 EclipseCon Eu 2013 - Living Documentation Slide 5 EclipseCon Eu 2013 - Living Documentation Slide 6 EclipseCon Eu 2013 - Living Documentation Slide 7 EclipseCon Eu 2013 - Living Documentation Slide 8 EclipseCon Eu 2013 - Living Documentation Slide 9 EclipseCon Eu 2013 - Living Documentation Slide 10 EclipseCon Eu 2013 - Living Documentation Slide 11 EclipseCon Eu 2013 - Living Documentation Slide 12 EclipseCon Eu 2013 - Living Documentation Slide 13 EclipseCon Eu 2013 - Living Documentation Slide 14 EclipseCon Eu 2013 - Living Documentation Slide 15 EclipseCon Eu 2013 - Living Documentation Slide 16 EclipseCon Eu 2013 - Living Documentation Slide 17 EclipseCon Eu 2013 - Living Documentation Slide 18 EclipseCon Eu 2013 - Living Documentation Slide 19 EclipseCon Eu 2013 - Living Documentation Slide 20 EclipseCon Eu 2013 - Living Documentation Slide 21 EclipseCon Eu 2013 - Living Documentation Slide 22 EclipseCon Eu 2013 - Living Documentation Slide 23 EclipseCon Eu 2013 - Living Documentation Slide 24 EclipseCon Eu 2013 - Living Documentation Slide 25 EclipseCon Eu 2013 - Living Documentation Slide 26 EclipseCon Eu 2013 - Living Documentation Slide 27 EclipseCon Eu 2013 - Living Documentation Slide 28 EclipseCon Eu 2013 - Living Documentation Slide 29 EclipseCon Eu 2013 - Living Documentation Slide 30 EclipseCon Eu 2013 - Living Documentation Slide 31 EclipseCon Eu 2013 - Living Documentation Slide 32 EclipseCon Eu 2013 - Living Documentation Slide 33 EclipseCon Eu 2013 - Living Documentation Slide 34 EclipseCon Eu 2013 - Living Documentation Slide 35 EclipseCon Eu 2013 - Living Documentation Slide 36 EclipseCon Eu 2013 - Living Documentation Slide 37 EclipseCon Eu 2013 - Living Documentation Slide 38 EclipseCon Eu 2013 - Living Documentation Slide 39 EclipseCon Eu 2013 - Living Documentation Slide 40 EclipseCon Eu 2013 - Living Documentation Slide 41 EclipseCon Eu 2013 - Living Documentation Slide 42 EclipseCon Eu 2013 - Living Documentation Slide 43 EclipseCon Eu 2013 - Living Documentation Slide 44
Prochain SlideShare
ETR2013 - Obeo Designer/Sirius
Suivant
Télécharger pour lire hors ligne et voir en mode plein écran

0 j’aime

Partager

Télécharger pour lire hors ligne

EclipseCon Eu 2013 - Living Documentation

Télécharger pour lire hors ligne

Documentation and tests are often considered as a write once and never look at again part of most projects, but we believe this isn’t a foregone conclusion. To this end, we’ve developed a new open source tool based on Mylyn Intent to provide a Living Documentation framework.

We need documentation that continues to evolve during the entire product lifetime and provides a single source of truth for our projects. So, we looked for a way to help our team maintaining a shared understanding and guaranteeing a consistent documentation. Even if this type of tool was not part of our usual toolset, we used Eclipse to create a living documentation tool which meets these needs.

After a quick presentation of our sources of inspiration (Acceptance testing, BDD - Behavior Driven Development, executable specification, Cucumber, Jnario...), we will expose the motivation behind the creation of this new tool.

We will show that it not only allows to keep the documentation up-to-date but also to generate the test code structure. Our purpose is to turn computer-focused tests into human-focused documentation. By using a well integrated business-readable syntax (based on Gerkhin) anyone can participate in the creation of specification and automated tests.

We are able to automatically synchronize the documentation with the code and all the existing artifacts of the project (build configuration files, models, source code, test code...).

Finally, a demonstration will show the numerous advantages offered by this approach:

Tests that are easier to read and focused on communication
Increase capabilities in the area of test automation and reduce duplication in the test code
Synchronization and easier navigation through the project artifacts
How are your applications documented? Do you have any documentation at all? If so, is it up-to-date and accurate? Attend this session and come to discuss with us on how to improve tools to document and test software in the 21st century.

  • Soyez le premier à aimer ceci

Documentation and tests are often considered as a write once and never look at again part of most projects, but we believe this isn’t a foregone conclusion. To this end, we’ve developed a new open source tool based on Mylyn Intent to provide a Living Documentation framework. We need documentation that continues to evolve during the entire product lifetime and provides a single source of truth for our projects. So, we looked for a way to help our team maintaining a shared understanding and guaranteeing a consistent documentation. Even if this type of tool was not part of our usual toolset, we used Eclipse to create a living documentation tool which meets these needs. After a quick presentation of our sources of inspiration (Acceptance testing, BDD - Behavior Driven Development, executable specification, Cucumber, Jnario...), we will expose the motivation behind the creation of this new tool. We will show that it not only allows to keep the documentation up-to-date but also to generate the test code structure. Our purpose is to turn computer-focused tests into human-focused documentation. By using a well integrated business-readable syntax (based on Gerkhin) anyone can participate in the creation of specification and automated tests. We are able to automatically synchronize the documentation with the code and all the existing artifacts of the project (build configuration files, models, source code, test code...). Finally, a demonstration will show the numerous advantages offered by this approach: Tests that are easier to read and focused on communication Increase capabilities in the area of test automation and reduce duplication in the test code Synchronization and easier navigation through the project artifacts How are your applications documented? Do you have any documentation at all? If so, is it up-to-date and accurate? Attend this session and come to discuss with us on how to improve tools to document and test software in the 21st century.

Vues

Nombre de vues

191

Sur Slideshare

0

À partir des intégrations

0

Nombre d'intégrations

1

Actions

Téléchargements

1

Partages

0

Commentaires

0

Mentions J'aime

0

×