TDD Vs BDD
TDD Vs BDD
2. EA S Y MA IN TE N A N CE CODE:
Working by necessity with code arranged in a specified
order is much easier when changes and modifications
need to be made. When developers work according to the
test-driven development approach, they naturally produce
cleaner, more readable, and manageable code.
3. R E FA C TOR C ON S TANTLY:
It’s always a good idea to review your work at the end of
each day. One strategy is to run all the tests, see where
they fail, and deal with them one by one. When you fix one
aspect of a program it can indirectly affect other parts that
were previously working fine.
BE N E F ITS OF BDD
1. A D DITION :
Behavior Driven Development (BDD) is a great way to work with
product teams to ensure that the right set of requirements is built
into the software being developed.
2. TR A NS PA RE N C Y:
When describing your product’s behavior, scenarios are concise
and easy to understand. Each scenario describes a unique
aspect of the experience. It makes it easier for the customer to
wrap their head around the whole idea in layman’s terms, so
they can accurately describe what they want when they want it.
3. WE L L -ORG A N IZE D:
BDD is designed to speed up the development process. Everyone
involved in development relies upon the same scenarios. Scenarios
are requirements, acceptance criteria, test cases, and test scripts all
in one – there is no need to write any other artifact. The modular
nature of Gherkin syntax expedites test automation development.
TEST-DRIVEN BEHAVIOR-DRIVEN
DEVELOPMENT (TDD) DEVELOPMENT (BDD)
@agilemania