StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
12753557
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-10-05T20:25:06.440
FavoriteCount
0
LastActivityDate
2012-10-05T20:25:06.440
LastEditDate
LastEditorUserId
0
OwnerUserId
1701085
ParentId
12728437
PostTypeId
2
Score
3
ViewCount
0
LastEditorDisplayName
text
Body
It will help if you could give some example of tests failures. Do the tests fail because they can't find some elements on the page ? If that's the case, if you are using WebDriver, I suggest you enable implicits waits. This will make your test suite run slower but you will gain stability. <pre><code>WebDriver driver = new FirefoxDriver(); driver.Manage().Timeouts().ImplicitlyWait(TimeSpan.FromSeconds(10)); </code></pre> Testing throught the browser, is something that can cause random failures specially if your tests are not designed to wait for elements to appear on the page. Things can get really tricky also with ajax calls. On a side note I'll recomend that you avoid running a new browser and start IIS before each tests. The reason is that your test suite will take a really long time to run. Instead I'd suggest that: - You run IIS just once in the begining of your test suite. (you can use the tag [BeforeTestRun]) - Open a browser session just once at the begining of your test suite. ([BeforeTestRun]) - At the end of each tests, just log out the user so that all cookies get cleaned. ([AfterScenario]) This will speed up your test suite a lots. Regarding shared state, I'd suggest that you reset all the data your tests use by using the attribute [BeforeScenario]. So for example, if your tests setup data in a database, you will clean the database before each test run. Finaly, make sure your tests are self contained: The should not use data used by other tests. The tests will need to always run from a clean initial state and create the data they need.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PORandomly failing Specflow tests
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USfoobarcode
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.