Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>You have several questions here, ill try to address them in a logical order</p> <p><strong>Is TDD a form of unit testing?</strong> </p> <p>Id say "yes", in the sense it creates unit tests, even if it isnt the only benefit of using TDD. On the topic stressed by commentators, but not mentioned in your question: TDD not only ensures test coverage and documentiation (good tests are one of the best form of low level code documentation). Using TDD forces you to make certain design decisions, usually improving the overall app design.</p> <p><strong>Do You write other tests?</strong></p> <p>Well, I don't write any other unit tests. The point of TDD is the development of the code parallel to the development of the tests. By writing software in a cycle - single test, only enough code to pass it, you're sure that your tests document all the functionality and behaviour you require from your code and you make sure that the code is testable (you have to write it that way doing TDD). There should be no need for additional unit tests</p> <p>There are other kinds of tests that you should use tho. Integration tests come to mind first, but there are other, like acceptance tests. If you have those automated, you will have it easier on you. Its not you who should be writing acceptance tests - it should be your customer/stakeholder, and You should be helping him on the technical part of writing them. You may be interested in Fitnesse <a href="http://fitnesse.org/" rel="nofollow">http://fitnesse.org/</a> - its a tool that helps non-technical people build acceptance tests.</p> <p><strong>About the stubbing?</strong></p> <p>Its kind of difficult to discuss this without concrete examples. All i can say right now is - just write the code one test at a time. If you do so, there are chances you wont encounter a situation where you have a complicated class and think about how to stub around its complex dependencies.</p> <p><strong>What tests should be included in the build?</strong></p> <p>Id say - all of them, if it is possible!</p>
    singulars
    1. This table or related slice is empty.
    1. POIs test driven development a form of unit testing
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USK.L.
    1. USK.L.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COAfter we completed the test-code-refactor process; at the end, we will have a series of test (TDD test) that verify only small unit of code for that whole class. But should we not test the whole control flow from entry point to exit point? What is your thoughts? In that sense, I tend to agree with @Jonathan Leffler that the TDD tests we write only serve to structure how our code will be. But to really assert whether those bits of code works well together, we need to have additional tests in the form of integration test?
      singulars
      1. PO
      1. USAshish
    2. COIn my understanding, integration tests are separate from unit tests and i agree they arent made during typical TDD, they have to be written separately, and they can be useful. Theyre exactly for the reason you mention: to check if those bits of code work **together**. Unit tests are for checking whether that code can work properly on its own :) Notice, that in my answer I wrote "I dont do any other **unit** tests" :)
      singulars
      1. PO
      1. USK.L.
    3. COAlthough, as mentioned by Carl, that TDD is a design methodology. The end product is that we will have a refactored code, with a series of "unit test" and any further change in one case can be checked for regression based on those "unit test" we wrote in the TDD process?
      singulars
      1. PO
      1. USAshish
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload