Downloaded 72 times
Uploaded byColin Wren
Continuous Integration, TDD & Living Documentation - Odoo Experience 2015
This document discusses continuous integration, test-driven development, living documentation, and how they can be applied to Odoo. It defines these terms and concepts: continuous integration automatically runs tests on merged code; test-driven development involves writing tests first before implementing code; and living documentation acts as project documentation, tests, and scope definition that evolves with a project. The document demonstrates how to create living documentation for Odoo using Behave and ERPPeek to run tests written in Gherkin, and shows an example output of the living documentation generated.
More Related Content
![[NDC16] (애드브릭스) 라이브마이그레이션 분투기 - 달리는 분석 툴의 바퀴를 갈아 끼워보자!](https://cdn.slidesharecdn.com/ss_thumbnails/ndc16-160427135233-thumbnail.jpg?width=640&height=640&fit=bounds)
![OpenGL Mini Projects With Source Code [ Computer Graphics ]](https://cdn.slidesharecdn.com/ss_thumbnails/newmicrosoftpowerpointpresentation-180330204024-thumbnail.jpg?width=640&height=640&fit=bounds)
Similar to Continuous Integration, TDD & Living Documentation - Odoo Experience 2015
Continuous Integration, TDD & Living Documentation - Odoo Experience 2015
- 1. Continuous Integration, TDD& Living Documentation with Odoo Colin Wren, Front end Dev & Dev Team Lead at Neova Health @colinwren colin@neovahealth.co.uk
- 2. Little about me Workfor Neova Health, based in London Been working with Odoo for last 2 years Using Odoo for Open-eObs, an electronic patient observation platform Odoo interests: Web Controllers, JavaScript and Testing
- 3.
- 4.
- 6. “What is ContinuousIntegration?”
- 7. Continuous Integration Merging developmentcode frequently into the codebase often to ensure it doesn’t break other code in the codebase by running unit test and integration test suites against newly merged code Automated via a Continuous Integration Engine such as Jenkins, Travis or Runbot which helps alleviate the need to spend developer time to run test suites Ideal for generating Living Documentation
- 8. “What is TestDriven Development and Behaviour Driven Development?”
- 9. Test/Behaviour Driven Development TestDriven Development Write tests first, implement later Helps you to think about what the code needs to achieve and then implement the functionality with that in mind Behaviour Driven Development Describe how features of the product work using business (or other) domain language Allows non-developers to write tests in their own domain language Developers run tests using Given, When, Then to test the output of the system when an event happens when the system is in a certain state
- 10. “What is LivingDocumentation?”
- 11. Living Documentation A singledocument that client, business team & development team use as a single point of scope Acts as project definition, test suite and client documentation Is an evolving document which helps to catch breaking scope changes or code changes over time Helps business team understand impact of scope changes on code base and vice versa Tests what a feature does not how it does it
- 12. Living Documentation forDevelopers Once scope for a feature is added it’s available for client, business and development This should prevent continual scope changes and creep As the document evolves the side effects of scope changes to established features are easily evidenced Test integration into documentation helps to show how much of features have been implemented as well history of tests
- 13. Living Documentation forBusiness Use Living Documentation to negotiate scope with clients and show them how changes will affect product Integration with test suite gives instant feedback on what has been implemented and what hasn’t Documentation is written as BDD tests are written
- 14. “How can thisbe applied to Odoo?”
- 15. Living Documentation withOdoo Disclaimer: At time of writing pull request is still pending Use Behave and ERPPeek to run tests (OERPScenario) Business team push BDD feature files to repo Development team push steps to same repo or different one used as submodule in git CI Engine listens to these repos and repos for product and run Behave test suites to generate Living Documentation and upload to webserver
- 16. “Demo - Creatinga task”
- 17.
- 18.
- 19.
- 20.
- 21.
- 22. “The Secret SauceSource”
- 23. It’s a BehaveReporter Behave exposes hooks for reporting plugins As the tests run I collect information on features, scenarios, steps & tags After the tests have run I use this information to match information in the config file and write the webpages using Jinja2
- 24.