Cucumber Framework

Root of any software is an Idea. The journey of Idea to software in any software company involves many minds starting from customer to software developer. Perfect communication and understanding is essential to make the idea to real software. As you probably know, good communication isn’t just about eloquently describing your ideas to others; you also need to solicit feedback to ensure you’ve been understood correctly. Below is an example on how miss communication and miss understanding would lead to failure.

If the developers spend considerable amount of time implementing a false understood idea, we can expect loss of productivity, also they’ve corrupted the integrity of the codebase with concepts and functionality that do not reflect the original idea. To come out of this untangle we can use Test Driven Development.

Test Driven Development

Instead of a customer passing requirements to the development team without much opportunity for feedback, the developer and customer collaborate to write automated tests that express the outcome that the stakeholder wants. We call them acceptance tests because they express what the software needs to do in order for the customer to find it acceptable. When we write these tests before development starts, we can explore and eradicate many misunderstandings long before they adverse effect on productivity and program. The test fails at the time of writing, because no code has been written yet, but it captures what the customer cares about and gives everyone a clear signal as to what it will take to be done.

Now customer has to write automated tests, should have coding knowledge which is least possible. In this case Cucumber framework is the solution.