unit testing - Why is design-by-contract not so popular compared to test-driven development? -


You might think that this question is like the previously asked question on the stack overflow. But I am trying to see things differently.

In TDD, we write tests that include different conditions, criteria, verification codes. If a class passes all these tests then we have a way to ensure that the class actually does this and nothing else.

If you follow the book Bertrand Meyers ' Object-oriented software creation by the word, the class has internal and external contracts, so it only

Ol>

  • Make a test to make sure that any values ​​ranges from (0-100) to all cases

  • method The exam passes.

    • DBC

    1. Create a class, create a contract for that member Virus to (0-100), the contract for contravention of contravention.

    I am in the same way as a DBC perspective.

    Is not Pure DBC so popular? Are these languages ​​or tools or are playful or is it just me who likes code for themselves?

    If you think that I am not thinking right, then I am ready to learn.

    In TDD, test (hopefully) well Based on current natural-text specifications of the documented method, a person has been written by. Thus, a man explains the correctness by writing the exam and takes some assurance on the basis of that interpretation.

    If you read the guide of the sun to write java docs, then it says that the documentation must have enough contract to compulsorily write the check plan. Therefore, the design by the contract is not mutually exclusive with TDD.


    Comments

    Post a Comment