Skip to main content

Test Driven Development (TDD)

Test Driven Development (TDD) is a software development practice that focuses on creating unit test cases before developing the actual code.

It is an iterative approach that combines programming, the creation of unit tests, and refactoring.

This is as opposed to software being developed first and test cases created later.


Rules for TDD:
  1. write a “single” unit test describing an aspect of the program
  2. run the test, which should fail because the program lacks that feature
  3. write “just enough” code, the simplest possible, to make the test pass
  4. “refactor” the code until it conforms to the simplicity criteria
  5. repeat, “accumulating” unit tests over time

Advantages of TDD:

  • You only write code that’s needed
  • More modular design
  • Easier to maintain
  • Easier to refactor
  • High test coverage
  • Tests document the code
  • Less debugging
Disadvantages of TDD:

  • Developer can consider it as a waste of time.
  • The test can be targeted on verification of classes and methods and not on what the code really should do.
  • Test become part of the maintenance overhead of a project.
  • Rewrite the test when requirements change.

Comments

Post a Comment

Popular posts from this blog

Certified Enterprise Architect Professional (CEAP) - Module 5 - Architecture Frameworks

Architecture Frameworks: An Architecture Framework is a theoretical structure that has the purpose of developing, executing, and maintaining an Enterprise Architecture. Advantages of EA framework: Simplify Breaks down areas of the business process Organise business components and create and identify relationships between business Determine the scope Customization in the existing framework Disadvantages of EA framework: Need to follow process Provides only direction and not information It's based on goal and objective Need creativity and proactive thinking Zachman Framework: The Zachman Framework is a widely used model in Enterprise Architecture (EA) that provides a structured way to classify and organize an organization's information infrastructure by defining different perspectives from various stakeholders, allowing for a holistic view of the enterprise and facilitating alignment between business needs and technology solutions; essentially acting as a template to organize arc...
Post a Comment
Read more

Daily Agile Scrum stand-up meeting guidelines

Followers of the Scrum method of project management will typically start their day with a " stand-up meeting ". In short, this is a quick daily meeting (30 minutes or less) where the participants share the answers to the three questions with each other: • What did I accomplish yesterday?  • What will I do today?  • What obstacles are impeding my progress?  Some people are talkative and tend to wander off into Story Telling .  Some people want to engage in Problem Solving immediately after hearing a problem. Meetings that take too long tend to have low energy and participants not directly related to a long discussion will tend to be distracted. These are the minimum number of questions that satisfy the goals of daily stand-ups. Other topics of discussion (e.g., design discussions, gossip, etc.) should be deferred until after the meeting.  Here are few tips for running a smooth daily meeting:  • Everyone should literally stand-up and no one should sit down ...
Post a Comment
Read more

Empiricism (Scrum)

Empiricism asserts that knowledge comes from experience and making decisions based on what is observed. Pillars of  Empiricism . Various practices exist to forecast progress, like burn-downs, burn-ups, or cumulative flows. While proven useful, these do not replace the importance of empiricism . In complex environments, what will happen is unknown. Only what has already happened may be used for forward-looking decision making. Each artifact contains a commitment to ensure it provides information that enhances transparency and focus against which progress can be measured: ● For the Product Backlog it is the Product Goal. ● For the Sprint Backlog it is the Sprint Goal. ● For the Increment it is the Definition of Done. These commitments exist to reinforce empiricism . The sum of the Increments is presented at the Sprint Review thus supporting empiricism .
Post a Comment
Read more