StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
16970088
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-06-06T18:59:58.487
FavoriteCount
0
LastActivityDate
2014-07-30T21:46:21.700
LastEditDate
2014-07-30T21:46:21.700
LastEditorUserId
467582
OwnerUserId
681187
ParentId
16800739
PostTypeId
2
Score
6
ViewCount
0
LastEditorDisplayName
text
Body
I've modified @Ben's <a href="http://jsfiddle.net/Q8TDa/4/" rel="nofollow" title="fiddle">fiddle</a> to include your code with both of your tests. I modified some of your code to make it run correctly. When you hit the run button all of the tests will pass. When you hit the run button again, the second test ("alternately passing and failing") will fail -- this is basically simulating your original issue. The issue is your first test ("always passing test") alters the global state by replacing the <code>jQuery.fn.on</code> function with an overridden one. Because of this, when the tests are run in order, the second test ("alternately passing and failing") uses the incorrect overridden <code>jQuery.fn.on</code> function and fails. Each unit test should return the global state back to its pre-test state so that other tests can run based on the same assumptions. The reason why it's alternating between pass and fail is that under the hood QUnit always runs failed tests first (it remembers this somehow via cookie or local storage, I'm not exactly sure). When it runs the failed tests first, the second test runs before the first one; as a result, the second test gets jQuery's native <code>on</code> function and works. When you run it a third time, the tests will run in their "original" order and the second test will use the overridden <code>on</code> function and fail. Here's the working <a href="http://jsfiddle.net/Q8TDa/5/" rel="nofollow" title="fiddle">fiddle</a>. I've add the fix to "un-override" the <code>on</code> function after the test by caching the original <code>var jQueryOn = jQuery.fn.on;</code> function and resetting it at the end of the test via: <code>jQuery.fn.on = jQueryOn;</code>. You can probably better implement this using QUnit's module <code>teardown()</code> method instead. You can check out <a href="https://github.com/jquery/qunit/issues/74" rel="nofollow">https://github.com/jquery/qunit/issues/74</a> for more info.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POQunit test alternates between pass and fail on page refresh
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USAndy Dvorak
UserOwnerUserId
1. USDragonDTG
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POQunit test alternates between pass and fail on page refresh
 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
 VTAcceptedByOriginator
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTBountyClose
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.