StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
7224449
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-08-28T22:39:51.290
FavoriteCount
0
LastActivityDate
2011-08-28T22:39:51.290
LastEditDate
LastEditorUserId
0
OwnerUserId
117104
ParentId
6715158
PostTypeId
2
Score
4
ViewCount
0
LastEditorDisplayName
text
Body
What version of Ruby are you using? In my understanding, 1.9 introduced <code>MiniTest</code>, which replaces <code>Test::Unit</code> entirely, with a backwards compatible API. So if you're on 1.9 and your Rails app references <code>Test::Unit</code>, it's actually already using <code>MiniTest</code>. Take a look at your Ruby source - <code>test/unit.rb</code> for 1.9.2 has the following requires: <pre><code>require 'minitest/unit' require 'test/unit/assertions' require 'test/unit/testcase' </code></pre> And <code>test/unit/assertions</code> includes <code>MiniTest::Assertions</code>. <hr> Getting your tests to run faster is a whole other dark art. Take a look at <a href="https://github.com/timcharper/spork" rel="nofollow">spork</a> and <a href="https://github.com/mynyml/watchr" rel="nofollow">watchr</a>. The former keeps your app initialized, reloads modified files, and forks before each run of your test suite. The latter watches files in your repo for changes, and automatically runs their associated test cases. Together they give you a pretty mean TDD setup. You write a test case for your new model, and it automatically runs and fails. Then whenever you save the associated model, that testcase re-runs, very quickly. You get near instant feedback on whether you're red/green. They're both a little tricky to get set up and behaving nicely together, so check back with some more questions if you get stuck. Best of luck!
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POHow to set up MiniTest?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USnfm
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
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.