StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
5584966
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-04-07T17:16:27.767
FavoriteCount
0
LastActivityDate
2011-04-07T23:16:03.890
LastEditDate
2011-04-07T23:16:03.890
LastEditorUserId
62002
OwnerUserId
62002
ParentId
5460531
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
look at the <code>HttpSessionStateBase</code> and <code>HttpSessionStateWrapper</code> classes in <code>System.Web.Abstractions</code>. <code>HttpSessionStateBase</code> is the abstract class from which <code>HttpSessionState</code> inherits, and <code>HttpSessionStateWrapper</code> is used to wrap a sealed class in an abstract class, which you can then mock in your tests. A lot of the <code>System.Web</code> classes are sealed (for example, <code>HttpSessionState</code>), so it's a real pain to test your code when you have methods and classes that interact with them. One pattern I like to use to get around this looks like the following: <pre><code>public void DoSomething(HttpSessionState state) { // take this HttpSeassionState and create an abstract HttpSessionStateBase // instance DoSomething(new HttpSessionStateWrapper(state)); } internal void DoSomething(HttpSessionStateBase state) { // my actual logic for working with the session state } </code></pre> The public method is difficult to test, because <code>HttpSessionState</code> is sealed, and you can't mock it. However, the internal method operates on an <code>HttpSessionStateBase</code> instance, which you can mock. Note that I've marked it as internal because I don't want the outside world to be able to access that method. However, I do want my tests to be able to access that, so I'll modify my AssemblyInfo.cs to include something like this: <pre><code>[assembly: InternalsVisibleTo("Vendor.Utilities.Tests")] </code></pre> Finally, my test for this would look something like this: <pre><code>[Test] public void Test_DoSomething() { HttpSessionStateBase state = MockRepository.PartialMock<HttpSessionStateBase>(); state.Expect(s => ...); MyClass.DoSomething(state); state.VerifyAllExpectations(); } </code></pre> Hope that helps. Good luck!
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POMocking HttpSessionState in ASP.net for nunit testing
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USmatt
UserOwnerUserId
1. USmatt
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
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.