1.

What Are The Benefits Of Tdd?

Answer»

Early bug notification:

Developers tests their code but in the database WORLD, this often consists of manual tests or one-off scripts. Using TDD you build up, over time, a suite of automated tests that you and any other developer can rerun at will.

Better Designed, CLEANER and more extensible code:

  • It helps to understand how the code will be used and how it interacts with other modules.
  • It results in better design decision and more maintainable code.
  • TDD allows writing smaller code having single responsibility rather than monolithic procedures with multiple responsibilities. This makes the code simpler to understand.
  • TDD also forces to write only production code to pass tests based on user requirements.

Confidence to Refactor:

  • If you refactor code, there can be possibilities of breaks in the code. So having a set of automated tests you can fix those breaks before release. Proper warning will be given if breaks found when automated tests are used.
  • Using TDD, should results in faster, more extensible code with fewer bugs that can be updated with minimal risks.

Good for teamwork:

In the absence of any team member, other team member can easily pick up and work on the code. It also aids KNOWLEDGE sharing, thereby making the team more effective overall.

Good for Developers:

Though developers have to spend more time in writing TDD test cases, it takes a LOT less time for DEBUGGING and developing new features. You will write cleaner, less complicated code.

Early bug notification:

Developers tests their code but in the database world, this often consists of manual tests or one-off scripts. Using TDD you build up, over time, a suite of automated tests that you and any other developer can rerun at will.

Better Designed, cleaner and more extensible code:

Confidence to Refactor:

Good for teamwork:

In the absence of any team member, other team member can easily pick up and work on the code. It also aids knowledge sharing, thereby making the team more effective overall.

Good for Developers:

Though developers have to spend more time in writing TDD test cases, it takes a lot less time for debugging and developing new features. You will write cleaner, less complicated code.



Discussion

No Comment Found