by Changepond Posted on July 10, 2018
Drive your agile project using Gherkin language to get the best out of Test Driven Development and for effective software delivery.
Today’s organisations are constantly challenged to modify and enhance their IT systems. Whether it is to keep up with the competition or meet the ever changing requirements from business stakeholders and customers, most organisations’ IT roadmap will inevitably feature multiple agile software development projects.
For large enterprises, these projects regularly raise challenges such as:
- Do all stakeholders fully understand the size and scope of the changes?
- How I can be confident that the new changes won’t break anything?
Over the years, TDD or Test Driven Development has gained popularity in agile projects. Test-Driven Development is the practice of writing a test for a piece of required functionality, before writing any implementation code. This test should fail when first run, and then, you write the code to make it pass. Once it does, you can safely refactor the code.
Most organisations shy away at the mention of TDD because they think it increases the amount of development time and requires significant effort at the start of the project to capture tests for all the requirements. However, Changepond has helped many of our customers incorporate TDD into their projects and we can confidently say that TDD has allowed them to develop the project much more quickly and with a higher quality.
The video below is a detailed introduction to TDD and the Gherkin language for capturing requirements. It’s also a case study on how we helped one of our existing customers incorporate a collaborative TDD methodology into their agile project.