StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
865614
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2009-05-14T20:36:48.677
FavoriteCount
0
LastActivityDate
2009-05-14T20:45:38.157
LastEditDate
2009-05-14T20:45:38.157
LastEditorUserId
28232
OwnerUserId
28232
ParentId
865559
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
You could look at wrapping all of the environmental settings that could change in a separate class that implements an interface. This could then be passed to the static method you have written which would then call back against the interface when it needs the various settings. This would allow you to mock the environmental settings to standardize when testing to prevent the issue you are seeing. It would also let you vary the settings to test different conditions. e.g. <pre><code>public interface IEnvironment { public bool SupportsIPV6 { get; } } </code></pre> And then your static method becomes. <pre><code>public static void DoSomething(IEnvironment environment) { if(environment.SupportsIPV6) { ... } } </code></pre> Then provide an implementation of IEnvironment that calls against the static System.Net method to get the actual setting for use, but a mock implementation for testing with a known value. If you don't want to pass the interface into the static method you could possibly look at implementing an object using the singleton pattern that then calls into this interface. The static method you have could then use the singleton to access whatever the current interface is although this method is a little messy so I'd probably go with the former. E.g. <pre><code>public Environment : IEnvironment { private static IEnvironment current = new Environment(); public static IEnvironment Current { get { return current; } set { current = value; } } public bool SupportsIPV6 { return System.Net..... } } </code></pre> Then call into it from your static method using. <pre><code>public static void DoSomething(IEnvironemnt environment) { if(Environment.Current.SupportsIPV6) { ... } } </code></pre> And you could change it in your tests via <pre><code>Environment.Current = new MockedEnvironment(); </code></pre> Although you'd need to watch out if you are doing any multithreading with a singleton like that.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POHow do I unit test for machine specific behaviour?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USRobG
UserOwnerUserId
1. USRobG
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.