Hot answers tagged

8

TDD (Test Driven Development) Who's involved: Developers Summary: Developers start writing code by first defining tests (in general unit tests). It could sound strange, but this practically guarantees a high code-coverage and in particular it forces developers to think about what they are doing. TDD can be applied to any kind of software. BDD (Behaviour ...


6

The short version: regardless of the development methodology, your role is to provide information about the overall quality of the application. You do that via testing anything that isn't included in the developer-maintained automation, and reviewing the developer-maintained automation. The long version: This question and its answers is a good starting ...


6

Both are a form of test driven development, since you write the tests upfront. The main difference is that TDD tests are technical tests often unit-tests created during developing of a feature and are written just before you implement a part of the feature in the code-base. Where BDD tests are often written before the coding starts and are human readable and ...


4

Adding my view points here. TL;DR : BDD focuses on the behavioural aspect of the system rather than the implementation aspect of the system that TDD focuses on. BDD gives a clearer understanding as to what the system should do from the perspective of the developer and the customer. BDD allows both the developer and the customer to work together to on ...


1

First of all, since you mention "through the testing", I would like to remark that TDD is more a design methodology than a testing one. This means that you don't have a specific testing phase, because tests are defined as a first step and then all coding should be aimed to get those tests pass. "The testing" is a continuous process that will check every code ...



Only top voted, non community-wiki answers of a minimum length are eligible