1
Sep

Role of Tester in Test Driven Development (TDD)

What is Test Driven Development Test driven development (TDD) was developed by Kent Beck as part of Extreme Programming in late 1990’s. This technique to build software follows three quite simple steps “Repeatedly”– Write a test for the next bit of functionality you want to add. Write the functional code until the test passes. Refactor both new and old code to make it well structured. Now the question is, since TDD is primarily a Programmer’s tool to help create well-written...Read More

1
Jan

Acceptance Test Driven Development (ATDD) example – Gherkin, SpecFlow and Nunit for Microsoft Platform (.Net/C#)

What is Acceptance Test Driven Development? ATDD is development methodology which promote good collaboration between business and technology group. There are many similar methodologies which works more or less same way like Behavior Driven Development (BDD), Example Driven Development (EDD) and Specification by Examples etc. ATDD is extended on TDD that emphasis on developers, testers and business collaboration. ATDD encompasses acceptance testing, but highlights writing acceptance tests before writing code. Acceptance Test Driven Development (ATDD) is a test first approach....Read More

31
Jul

Defects are not Technical Debts

Many people get confused between technical debts and non-functional requirements. Defects can't be technical debts because technical debts doesn't mean not meeting requirement either functional or technical. Technical debts are related to poor design, poor coding or not having applied appropriate design patterns etc. Whereas defects are not meeting requirement, product not fit for use or poor performance etc. Many time these confusions are created by agile doctors (agile coaches). May be those doctors are not from development background or...Read More