StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
8468411
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-12-11T23:33:43.213
FavoriteCount
0
LastActivityDate
2011-12-11T23:33:43.213
LastEditDate
LastEditorUserId
0
OwnerUserId
680920
ParentId
8392692
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
One thing I would recommend no matter what testing framework you are using is type-hinting against the expected class, or interface. <pre><code><?php class ExampleClass { private $OtherClass; // OtherClass instance public function __construct(OtherClass $OtherClass=null) { // ... } } </code></pre> I'm no di expert, but I don't see the problem in letting each class call new if an instance isn't provided for a particular dependency. You could also of course take the approach where you use setter methods to configure dependencies. <pre><code><?php class class ExampleClass { private $OtherClass; // OtherClass instance public function setOtherClass(OtherClass $OtherClass) { $this->OtherClass = $OtherClass; } } </code></pre> It is lame that the ExampleClass in the sample code doesn't even define the doSomething method from the ExampleDependencyClassTests, but if I understand correctly it looks like Enhance PHP is not forcing you to take a particular style of dependency injection. You can write the test class however you want, so for example if you took the setter method approach I mentioned above, you could change the example mock code to <pre><code><?php class ExampleDependencyClassTests extends \Enhance\TestFixture { public function verifyWithAMock() { $mock = \Enhance\MockFactory::createMock('ExampleDependencyClass'); $mock->addExpectation( \Enhance\Expect::method('getSomething') ->with(1, 'Arg2') ->returns('Something') ->times(1) ); $target = new ExampleClass(); $target->setExampleDependencyClass($mock); $result = $target->doSomething(); $mock->verifyExpectations(); } } </code></pre> Of course it would probly make sense to make the appropriate revisions to the ExampleClass! <pre><code><?php class ExampleClass { private $ExampleDependencyClass; public function addTwoNumbers($a, $b) { return $a + $b; } public function setExampleDependencyClass( ExampleDependencyClass $ExampleDependecyClass ) { $this->ExampleDependecyClass = $ExampleDependecyClass; } public function doSomething($someArg) { return 'Something'; } } </code></pre> I've worked with PHPUnit quite a bit, and honestly you'll have to face the same challenges with Mocks there. My 2 cents, try to model your tests without Mocks if possible ;)
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POGetting started with "Enhance PHP"
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USquickshiftin
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
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.