StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
1039060
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2009-06-24T15:20:21.643
FavoriteCount
0
LastActivityDate
2009-06-24T15:20:21.643
LastEditDate
LastEditorUserId
0
OwnerUserId
126992
ParentId
1038790
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
It's unfortunate that you're using <code>getResultState()</code> to create the <code>ResultState</code> object, itself, which is really your blocker. Consider refactoring into the following interface: <pre><code>protected ResultState initResultState ( ) { this.resultState = new ResultState(); // Initialization Logic... return this.resultState; } // END initResultState public ResultState getResultState ( ) { if ( this.resultState === null ) { return this.initResultState(); } return this.resultState; } // END getResultState() </code></pre> From this position, it's easier to test your getter method. Define a descendant class that returns a known <code>ResultState</code> Stub for <code>initResultState()</code> that can be interrogated, ie: <pre><code>/** * The test fixutre's initResultState() method merely returns a simple Stub of * the ResultState object, which can be more easily interrogated. */ public ResultState initResultState ( ) { return new Stub_ResultState(); } // END initResultState </code></pre> That still leaves you with the protected <code>initResultState()</code>, of course. Consider the following refactoring: <pre><code>protected ResultState initResultState ( ResultState newResultState ) { this.resultState = newResultState; // Initialization Logic... return this.resultState; } // END initResultState public ResultState getResultState ( ) { if ( this.resultState === null ) { return this.initResultState( new ResultState() ); } return this.resultState; } // END getResultState </code></pre> This permits you to override the <code>getResultState()</code> method in a descendant class such that you can pass another <code>ResultState</code> Stub object to be manipulated and interrogated afterward, for example: <pre><code>/** * The test fixture's getResultState() method always acts as a passthrough for * initResultState(), which is protected, so that the output of the protected * method can be interrogated. */ public ResultState getResultState ( ) { return this.initResultState( new Stub_ResultState() ); } // END getResultState </code></pre> From this position, you need two test fixtures: one that overrides the behavior of <code>initResultState()</code> to test the functionality of the getters; another that overrides the behavior of <code>getResultState()</code> to test the behavior of <code>initResultState()</code>. Both use an instance of the <code>Stub_ResultState</code> class, which is necessarily a descendant of the <code>ResultState</code> class but provides public access to the internal values of its parent object for interrogation in unit tests. I hope that makes sense, but feel free to ask for clarifications.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POunit testing a method that returns a non trivial object
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USAL the X
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
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.