Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Many great responses to this are also on my question: "<a href="https://stackoverflow.com/questions/24965/beginning-tdd-challenges-solutions-recommendations">Beginning TDD - Challenges? Solutions? Recommendations?</a>"</p> <p>May I also recommend taking a look at my <a href="http://cantgrokwontgrok.blogspot.com/2008/09/tdd-getting-started-with-test-driven.html" rel="noreferrer">blog post</a> (which was partly inspired by my question), I have got some good feedback on that. Namely:</p> <blockquote> <p><strong>I Don’t Know Where to Start?</strong></p> <ul> <li>Start afresh. Only think about writing tests when you are writing new code. This can be re-working of old code, or a completely new feature.</li> <li>Start simple. Don’t go running off and trying to get your head round a testing framework as well as being TDD-esque. Debug.Assert works fine. Use it as a starting point. It doesn’t mess with your project or create dependencies.</li> <li>Start positive. You are trying to improve your craft, feel good about it. I have seen plenty of developers out there that are happy to stagnate and not try new things to better themselves. You are doing the right thing, remember this and it will help stop you from giving up.</li> <li>Start ready for a challenge. It is quite hard to start getting into testing. Expect a challenge, but remember – challenges can be overcome.</li> </ul> <p><strong>Only Test For What You Expect</strong></p> <p>I had real problems when I first started because I was constantly sat there trying to figure out every possible problem that could occur and then trying to test for it and fix. This is a quick way to a headache. Testing should be a real YAGNI process. If you know there is a problem, then write a test for it. Otherwise, don’t bother.</p> <p><strong>Only Test One Thing</strong></p> <p>Each test case should only ever test one thing. If you ever find yourself putting “and” in the test case name, you’re doing something wrong.</p> </blockquote> <p>I hope this means we can move on from "getters and setters" :)</p>
    singulars
    1. This table or related slice is empty.
    1. POHow do you know what to test when writing unit tests?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USCommunity
    1. USRob Cooper
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POHow do you know what to test when writing unit tests?
      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. CO"If you know there is a problem, then write a test for it. Otherwise, don’t bother." I would disagree with the way this is worded. I was under the impression that unit tests should cover all possible execution paths.
      singulars
      1. PO
      1. USCorin Blaikie
    2. COWhile some may advocate such things, I personally don't. A good 90% of my headache came from simply trying to do "everything". I say test for what you expect to happen (so you know you are getting the right values back) but don't try and figure it all out. YAGNI.
      singulars
      1. PO
      1. USRob Cooper
    3. COI, too, advocate the "test your bugs" approach. If we all had infinite time and patience, we'd test every possible execution path. But we don't, so you have to spend your effort where it's going to have the greatest effect.
      singulars
      1. PO
      1. USSchwern
 

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