StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
19907985
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2013-11-11T13:48:15.713
FavoriteCount
0
LastActivityDate
2013-11-11T13:55:49.703
LastEditDate
2013-11-11T13:55:49.703
LastEditorUserId
1412984
OwnerUserId
1412984
ParentId
19896689
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
<h2>Mocking a connection</h2> <p>Mocking a database connection gets complicated (<a href="https://github.com/fideloper/ResourceCache/blob/master/tests/EloquentResourceTest.php#L73" rel="nofollow">I've done it before, it's messy!</a>). </p> <p>This is some code I had working in <a href="https://github.com/fideloper/ResourceCache/blob/master/tests/EloquentResourceTest.php" rel="nofollow">a unit test</a> after a ton of trial and error some months ago:</p> <pre><code>Illuminate\Database\Eloquent\Model::setConnectionResolver($resolver = m::mock('Illuminate\Database\ConnectionResolverInterface')); $resolver->shouldReceive('connection')->andReturn($mockConnection = m::mock('Illuminate\Database\ConnectionInterface')); $mockConnection->shouldreceive('getPostProcessor')->andReturn(m::mock('Illuminate\Database\Query\Processors\Processor')); $mockConnection->shouldReceive('getQueryGrammar')->andReturn($queryGrammar = m::mock('Illuminate\Database\Query\Grammars\Grammar')); $queryGrammar->shouldReceive('getDateFormat')->andReturn('Y-m-d H:i:s'); </code></pre> <h2>Using sqllite</h2> <p>I will suggest, then, to actually use a sqlite database for testing database connections. I've found this much easier. </p> <p>Testing with PHPunit triggers the <code>testing</code> environment in Laravel, so you can define an in-memory (only on for that request) sqlite database connection on that environment and and even seed it in your test setup. </p> <p>Here's a sample gist for <a href="https://gist.github.com/fideloper/7413518" rel="nofollow">testing using an in-memory sqlite database</a>.</p> <h2>Testing things already tested</h2> <p>Your unit test here might be simplistic for example, I'm not sure - However, you're testing something that's <a href="https://github.com/laravel/framework/blob/master/tests/Database/DatabaseEloquentModelTest.php" rel="nofollow">already tested in Laravel</a>. Consider carefully what you decide to test :D</p>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POHow can I test Eloquent in Workbench?
  singulars
  PostTypePostTypeId
  PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USfideloper
UserOwnerUserId
1. USfideloper
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. This table or related slice is empty.
CommentsPostId
1. COEdited with some development. I got it all working, except for Artisan.
  singulars
  PostPostId
  PO
  UserUserId
  USAntonio Carlos Ribeiro

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.