StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
13080103
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-10-26T02:51:01.173
FavoriteCount
0
LastActivityDate
2012-10-26T02:51:01.173
LastEditDate
LastEditorUserId
0
OwnerUserId
635981
ParentId
13078848
PostTypeId
2
Score
3
ViewCount
0
LastEditorDisplayName
text
Body
So here's what I see people doing, and the method I've adopted in my own work: <ol> <li>In your modules, only export the values that need to be exported. Personally, I try to limit myself to exporting no more than a single function but that's a separate discussion.</li> <li>Create a <code>test</code> directory and place all of your test cases in it. Use whatever naming convention you like. I prefer to have one test file for each source module. At the start of each file, simply require the module under test.</li> <li>Call mocha from a Makefile/Cakefile with the <code>--recursive</code> argument so it knows to examine the entire contents of your <code>test</code> directory.</li> </ol> This means you are testing the modules through their interfaces, just as you would use them in normal code. The downside is, if you have non-exported functions with execution paths which are difficult to hit via the module's interface, you may find yourself a little frustrated. On one hand, I agree with the notion that modules should be tested as they are used. On the other hand I think I'd sleep better at night knowing that I directly tested every one of the aforementioned tricky execution paths. Prior to doing node.js programming I spent several years writing erlang code, which has the exact opposite convention: (tests are placed at the end of the source files so they have direct access to every function in the module, and testing includes/exports are handled by ifdef directives). Personally, I like the erlang approach better. Anyway, I hope this was helpful. If anyone reading this has a strong opinion to the contrary I'd love to hear it.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POunobtrusive node testing
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USDavid Weldon
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
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.