StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
8009392
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-11-04T12:48:12.633
FavoriteCount
0
LastActivityDate
2011-11-04T12:48:12.633
LastEditDate
LastEditorUserId
0
OwnerUserId
731115
ParentId
7694010
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
Main issue here is that you mix different layers. Repository is a intermediate level between Business Logic and storage. If your case, repository performs actions which are the part of Business logic. That's why you're forced to mimic that in your tests. In general your entity should be fully constructed prior to saving. Repository should only save it (probably, invoking Validate method, if you need that). This code: <pre><code>couple.Bride.Gender = Gender.Female; couple.Groom.Gender = Gender.Male; </code></pre> should be moved to Couple business logic (constructor, for example). From the more global point of view, with TDD you make mocks around the functionality you want to test. With your current approach you'll probably have something like <code>IView -> Couple class -> IRepository</code> chain. That means that by mocking those interfaces, you intend to test Couple class (or business logic work in general). To test the repository, you need a structure like <code>Couple class -> CoupleRepository -> IDatabaseDriver</code> sequence. By mocking <code>IDatabaseDriver</code> you'll be able to verify SqlCommands or Queries generated by real implementation of CoupleRepository. In that case you'll write tests like (very simplistic sample): <pre><code>var driver = new MockDatabaseDriver(); var repo = CoupleRepository(MockDatabaseDriver); repo.Add(new Couple()); Assert.AreEquals("Insert into COUPLES values ('bride', groom')", driver.SqlQueryText); </code></pre> Here MockDatabaseDriver doesn't execute queries, just indicates actions performed by repository.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POQuestions about TDD
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USmikalai
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POQuestions about TDD
 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
 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.