Test Driven Development (TDD) and (BDD) Behaviour Driven Developement

Test driven development simply put is to write a test first, write the code for it, and then (eventually) pass that test. This is done in short development cycles, so the team keep writing tests and then writing the code to pass the tests on a continuous basis.

A brief video explaining TDD:

Its worth noting that BDD (Behaviour driven development) emerged from TDD and below is a good video on TDD and BDD – What Are The Key Differences?

Below is another interesting video on TDD vs BDD. In this case BDD comes out as a winner for it reduces the amount of work required, and also delivers on the required quality.

Here is a link from TechTarget to a more detailed description of BDD and an extract below from the article.

“Behavior-driven development (BDD) is a software development methodology in which an application is specified and designed by describing how its behavior should appear to an outside observer.”

Software Development Life Cycle – Summary

Here is a link to a useful and interesting overview of the Software Development Life Cycle “SDLC.”

sdlc_stagesAn interesting read for anyone new or just getting into software development. It does appear to outline a some what Waterfall approach in the body of the article – which these days is a method no longer used, or being used less and less. However, at the bottom it does out line different models for software development including that of Agile and Waterfall.

I would also add that it’s really important to test as you proceed the build and not to start testing once the build is completed!

Stage 5: Testing the Product

This stage is usually a subset of all the stages as in the modern SDLC models, the testing activities are mostly involved in all the stages of SDLC. However this stage refers to the testing only stage of the product where products defects are reported, tracked, fixed and retested, until the product reaches the quality standards defined in the SRS.