StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
11263397
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-06-29T14:13:29.477
FavoriteCount
0
LastActivityDate
2012-06-29T14:30:24.360
LastEditDate
2012-06-29T14:30:24.360
LastEditorUserId
343266
OwnerUserId
343266
ParentId
11262398
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
I have found custom failure message helpful in rather limited number of cases. Particulary, when you assert several properties of objects which expected/actual values might not give the best information about what (and why) failed. Consider a test such as: <pre><code>[Test] public void CreateOrder_CreatesValidOrderForProvidedCustomer() { // Assume we arranged test here var order = orderFactory.Create(customer); Assert.That(order.Type, Is.EqualTo("Immediate Dispatch")); Assert.That(order.Details, Is.EqualTo("Very Important Package")); Assert.That(order.CustomerNote, Is.EqualTo("Send fast or I tell mom")); } </code></pre> When any of the asserts above fails, message you'll get will be something along the lines: <blockquote> Expected: "Very Important Package" Actual: "Dispatch quickly". </blockquote> It's hard to tell which property caused that without looking at unit test (data it uses to be precise). Simply adding property name as a failure message helps here. But! This was just extreme case, when multiple asserted properties might be hard to differentiate content-wise. Usually, you shouldn't be facing such problems (note that we solved it with providing one word long expection message). If you feel the need to use long and descriptive expection message, it might be a sign that your test is overly complicated. You might consider splitting it into few tests, or maybe even redesigning tested class. On top of that, I suggest having a look at projects like <a href="http://fluentassertions.codeplex.com/" rel="nofollow">FluentAssertions</a>. They got it right: <blockquote> Nothing is more annoying then a unit test that fails without clearly explaining why. </blockquote> And solved the issue with very clean syntax and neat error reporting: <pre><code>"1234567890".Should().Be("0987654321"); </code></pre> Will be reported as: <blockquote> Expected string to be "0987654321", but "1234567890" differs near "123" (index 0). </blockquote>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PORecommended standards for unit test failure messages?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USk.m
UserOwnerUserId
1. USk.m
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. PORecommended standards for unit test failure messages?
 singulars
 PostTypePostTypeId
 PTQuestion
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
 VTAcceptedByOriginator
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.