StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
838781
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2009-05-08T08:24:26.753
FavoriteCount
0
LastActivityDate
2009-05-08T08:59:07.840
LastEditDate
2009-05-08T08:59:07.840
LastEditorUserId
39709
OwnerUserId
39709
ParentId
838770
PostTypeId
2
Score
11
ViewCount
0
LastEditorDisplayName
text
Body
<h2>From a training/process point of view:</h2> <p>Train your team to know that "works on my machine" is not a get-out-of-jail-free response.</p> <p>Have an <a href="http://confluence.public.thoughtworks.org/display/CCNET/Welcome+to+CruiseControl.NET" rel="noreferrer">automated build server</a>.</p> <p>Have an automated test deployment.</p> <p>Your developers must know that "works" is defined as "works on the test server", not just their machine.</p> <h2>From a testing/debugging point of view:</h2> <p>The developer needs to be shown the sequence of actions that result in the bug happening.</p> <p>You might want to capture screenshots showing the bug, or possibly a video capture (using tools such as <a href="http://www.techsmith.com/camtasia.asp" rel="noreferrer">Camtasia</a>). People can be quite bad at describing the sequence of actions that they performed on a system that led to a bug showing itself, so the more information you can capture about the bug and how to replicate itself the better.</p> <h2>From a development/environment point of view:</h2> <p>If there is genuinely a bug that exhibits itself on one environment but not the developer's then find out if it exhibits itself on no development environments, or just your one developer's.</p> <p>From thereon in it is a case of trying to reduce the differences between the two environments so that your developer can see the issue on his machine.</p> <p>Or you can go the other way and attempt to debug the issue on the production (non-development) environment.</p> <p>Implementation details of these vary by platform.</p>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POhow do you troubleshoot with "works on my machine" scenarios
  singulars
  PostTypePostTypeId
  PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USRichard Everett
UserOwnerUserId
1. USRichard Everett
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POhow do you troubleshoot with "works on my machine" scenarios
  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
  VTUpMod
3. 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.