Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <blockquote> <p>What do you mean by saying "You're protected from regressing it, because that test will suddenly fail."?</p> </blockquote> <p>The point of "unit tests" is that they will be run automatically as part of the compile/check cycle: you'll run the tests after compiling and before checking code in. If a unit test fails, then you know that some code that <strong>you just wrote</strong> will recreate the old bug. </p> <p>edit: </p> <blockquote> <p>How can you be so sure that just because your unit tests passed all your bugs have been fixed.</p> </blockquote> <p>Generally, if you can reproduce a bug, you can make a test to duplicate it in code. The most important part is once you've written a test to check for the existance of a bug, then if you run the tests, and the test fails, then you reintroduced the bug. One great book on the subject is <a href="http://rads.stackoverflow.com/amzn/click/0131177052" rel="nofollow noreferrer" title="Working Effectively with Legacy Code">"Working Effectively with Legacy Code"</a></p> <blockquote> <p>Is it not possible for a single bug to span multiple unit tests.</p> </blockquote> <p>Of course it can span multiple tests.</p> <p>Let's presume the bug is "can't save files." </p> <p>And let's presume that there are several different scenarios that can cause this: </p> <ul> <li><p>out of disk space,</p></li> <li><p>the file you're writing on top of is opened and locked by another process,</p></li> <li><p>there are permissions problems (like you can't access the directory, or don't have write permissions),</p></li> <li><p>or there is a network error while you're saving the file.</p></li> </ul> <p>Ideally, your test harness (a collection of tests) would have a separate test for each one. For some of the tests, you may need to use stuff that are called "mock objects" (they can also be used when you haven't written the code for the component yet).</p>
    singulars
    1. This table or related slice is empty.
    1. POHow do you ensure the same bug does not creep into the product the second time?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USTangurena
    1. USTangurena
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POHow do you ensure the same bug does not creep into the product the second time?
      singulars
      1. PTQuestion
    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. CODo bugs and unit tests have one to one correspondence? Is it not possible for a single bug to span multiple unit tests. How can you be so sure that just because your unit tests passed all your bugs have been fixed.
      singulars
      1. PO
      1. USmsvcyc
    2. COmsvcyc: You cannot be sure you have no bugs when all your tests pass, but you can be sure none of the bugs detected by your tests are present. (Your policy on writing tests and what bugs your tests actually detect is another matter.)
      singulars
      1. PO
      1. This table or related slice is empty.
 

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