StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
1014560
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2009-06-18T18:59:42.637
FavoriteCount
0
LastActivityDate
2009-06-21T13:02:50.703
LastEditDate
2009-06-21T13:02:50.703
LastEditorUserId
97443
OwnerUserId
97443
ParentId
155436
PostTypeId
2
Score
6
ViewCount
0
LastEditorDisplayName
text
Body
I recently came up with the following convention for naming my tests, their classes and containing projects in order to maximize their descriptivenes: Lets say I am testing the Settings class in a project in the MyApp.Serialization namespace. First I will create a test project with the MyApp.Serialization.Tests namespace. Within this project and of course the namespace I will create a class called IfSettings (saved as IfSettings.cs). Lets say I am testing the SaveStrings() method. -> I will name the test CanSaveStrings(). When I run this test it will show the following heading: MyApp.Serialization.Tests.IfSettings.CanSaveStrings I think this tells me very well, what it is testing. Of course it is usefull that in English the noun "Tests" is the same as the verb "tests". There is no limit to your creativity in naming the tests, so that we get full sentence headings for them. Usually the Testnames will have to start with a verb. Examples include: <ul> <li>Detects (e.g. DetectsInvalidUserInput)</li> <li>Throws (e.g. ThrowsOnNotFound)</li> <li>Will (e.g. WillCloseTheDatabaseAfterTheTransaction)</li> </ul> etc. Another option is to use "that" instead of "if". The latter saves me keystrokes though and describes more exactly what I am doing, since I don't know, that the tested behavior is present, but am testing if it is. [Edit] After using above naming convention for a little longer now, I have found, that the If prefix can be confusing, when working with interfaces. It just so happens, that the testing class IfSerializer.cs looks very similar to the interface ISerializer.cs in the "Open Files Tab". This can get very annoying when switching back and forth between the tests, the class being tested and its interface. As a result I would now choose That over If as a prefix. Additionally I now use - only for methods in my test classes as it is not considered best practice anywhere else - the "_" to separate words in my test method names as in: <ul> <li>[Test] public void detects_invalid_User_Input() *</li> </ul> I find this to be easier to read. [End Edit] I hope this spawns some more ideas, since I consider naming tests of great importance as it can save you a lot of time that would otherwise have been spent trying to understand what the tests are doing (e.g. after resuming a project after an extended hiatus).
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POUnit test naming best practices
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USThorsten Lorenz
UserOwnerUserId
1. USThorsten Lorenz
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. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
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.