#1169 DDC-3343 - updating test expectations - one-to-many changes should be no-op unless orphan removal is specified.
This commit is contained in:
parent
9839c400b8
commit
539c364ca6
@ -485,7 +485,7 @@ class ExtraLazyCollectionTest extends OrmFunctionalTestCase
|
||||
|
||||
$this->assertFalse($user->articles->isInitialized(), "Post-Condition: Collection is not initialized.");
|
||||
// NOTE: +2 queries because CmsArticle is a versioned entity, and that needs to be handled accordingly
|
||||
$this->assertEquals($queryCount + 2, $this->getCurrentQueryCount());
|
||||
$this->assertEquals($queryCount, $this->getCurrentQueryCount());
|
||||
|
||||
// Test One to Many removal with Entity state as new
|
||||
$article = new \Doctrine\Tests\Models\CMS\CmsArticle();
|
||||
@ -1123,7 +1123,7 @@ class ExtraLazyCollectionTest extends OrmFunctionalTestCase
|
||||
'Even though the collection is extra lazy, the tweet should not have been deleted'
|
||||
);
|
||||
|
||||
$this->assertNull($tweet->author);
|
||||
$this->assertInstanceOf(User::CLASSNAME, $tweet->author);
|
||||
|
||||
/* @var $user User */
|
||||
$user = $this->_em->find(User::CLASSNAME, $userId);
|
||||
|
Loading…
x
Reference in New Issue
Block a user