PHPUnit Test assertions different after upgrade from 3.6.6 to 3.7.5Best practices to test protected methods with PHPUnitPHPUnit assert that an exception was thrown?Difference between assertEquals and assertSame in phpunit?How to run single test method with phpunit?datasource configuration “default” was not found in CakePHP 3PHPUnit testing a flash message with a key and parameters in CakePHP 3.5Cakephp 3 PHPUnit ingration test fails after the test beforePhpunit test neither outputs nor throws errorsPHPUnit testing a cell not working with set but does with return?write phpunit test function for a service class
How did Apollo 15's depressurization work?
Story about a demon trying to make a man insane
Homogeneous Equations and Linear Algebra
How to dismiss intrusive questions from a colleague with whom I don't work?
Starships without computers?
Has there ever been a truly bilingual country prior to the contemporary period?
What happened after the end of the Truman Show?
Is "stainless" a bulk or a surface property of stainless steel?
Limits and Continuity in Multi variable calculus.
How can I get rid of this Lazy Spool, or otherwise improve this query's performance?
How can I describe being temporarily stupid?
Could sidesticks be linked?
How does the Saturn V Dynamic Test Stand work?
Why does AC run even when it is cooler outside than in?
Is it allowable to use an organization's name to publish a paper in a conference, even after I graduate from it?
TechSupport Issue ID#812
Do living authors still get paid royalties for their old work?
Is this kind of description not recommended?
Does the Green Flame-Blade cantrip work with the Zephyr Strike spell?
Why is su world executable?
Is there such a thing as too inconvenient?
Unbiased estimator of exponential of measure of a set?
Can I submit a paper under an alias so as to avoid trouble in my country?
My two team members in a remote location don't get along with each other; how can I improve working relations?
PHPUnit Test assertions different after upgrade from 3.6.6 to 3.7.5
Best practices to test protected methods with PHPUnitPHPUnit assert that an exception was thrown?Difference between assertEquals and assertSame in phpunit?How to run single test method with phpunit?datasource configuration “default” was not found in CakePHP 3PHPUnit testing a flash message with a key and parameters in CakePHP 3.5Cakephp 3 PHPUnit ingration test fails after the test beforePhpunit test neither outputs nor throws errorsPHPUnit testing a cell not working with set but does with return?write phpunit test function for a service class
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;
A couple of days ago I upgraded my app from 3.6.6 to 3.7.5. Before I did the upgrade I ran all my tests which provided the following results:
// Environment
CakePHP Version: 3.6.6
PHPUnit Version: 6.5.14
// Results
Tests: 476, Assertions: 1927
// Sublime Text 3 find with $this->assert
1038 $this->assert's found.
Therefore: 1038 $this->assert found and 1927 assertions in results.
// Controller Test
use CakeTestSuiteIntegrationTestCase;
class UsersControllerTest extends IntegrationTestCase
{
======================================================================
I created a new project with composer self-update && composer create-project --prefer-dist cakephp/app app_name.
I copied all the files over and implemented the changes documented in the migration guide.
I logged in and everything worked (Except for the middleware csrf token mismatch error but thats another issue.)
I ran my tests again and the following results where provided.
// Environment
CakePHP Version: 3.7.5
PHPUnit Version: 6.5.8
// Results
Tests: 497, Assertions: 1135
// Sublime Text 3 find with $this->assert
1059 $this->assert's found.
Therefore: 1059 $this->assert found and 1135 assertions in results.
// Controller Test
use CakeTestSuiteTestCase;
use CakeTestSuiteIntegrationTestTrait;
class UsersControllerTest extends TestCase
{
use IntegrationTestTrait;
======================================================================
I've double checked I copied everything over accurately and everything is as it should be apart from understanding
the test results.
I also used Sublime Text 3 to check that I hadn't called $this->assert 792 more times after my upgrade but this confirmed it's been called the correct amount of times taking into consideration I did 21 more tests.
The only differences I can see are:
- In 3.6.6 IntegrationTestCase is used.
In 3.6.6 PHPUnit Version: 6.5.14 is used.
In 3.7.5 TestCase and IntegrationTestTrait is used.
- In 3.7.5 PHPUnit Version: 6.5.8 is used.
======================================================================
// Question:
I'm hoping someone can help me understand why I can do 21 more tests but have 792 less assertions? Is it the use of TestCase and IntegrationTestTrait instead of IntegrationTestCase or the PHPUnit version difference or maybe something else?
Thanks. Z.
======================================================================
@ndm, thanks for the input.
I would like to follow your advice but the situation has changed. I got up this morning and tried to replicate the results from yesterday. My new 3.7.5 app test results were the same:
// Environment
CakePHP Version: 3.7.5
PHPUnit Version: 6.5.8
// Results
Tests: 497, Assertions: 1135
Then I loaded my old 3.6.6 app and ran the tests again but the PHPUnit version had changed and these were the results:
// Environment
CakePHP Version: 3.6.6
PHPUnit Version: 6.5.8
// Results
Tests: 497, Assertions: 1135
I thought I'd made a mistake yesterday and copied the wrong folder so I got my master backups out which hadn't been touched (All the way back to 19/01/19). I loaded 4 backups all on CakePHP version 3.6.6. All of them show these results.
// Environment
CakePHP Version: 3.6.6
PHPUnit Version: 6.5.8
// Results
Tests: 497, Assertions: 1135
So now I'm wondering where on earth is PHPUnit 6.5.14?
Since 19/01/19 I've run my tests on my CakePHP 3.6.6 apps about 50 times and when you run the test the cmd line always displays the PHPUnit version so I know I was using PHPUnit 6.5.14.
And now I'm wondering what could explain this? This also means I cannot replicate the results from yesterday.
Your advice has put my mind at rest, ie: it could be a lot of different things. Also I need to weigh up the time it would take me to isolate the reason against the benefits of knowing the reason.
For the moment I've decided to put this issue on my to do list seeing as it still does run all the tests and it could be as you mention "Maybe some assertion methods provided by CakePHP changed so that they internally make less calls to PHPUnit assertion methods. Maybe PHPUnit wasn't calculating things incorrectly in earlier versions. Maybe something totally different, there could be lots of reasons" and it's an unknown amount of time to get to the bottom of.
Hopefully within the next couple of months I can free up some time to get into it but for the moment I've filed it under "Sherlock Holmes and the case of the missing PHPUnit version". :)
Thanks again, Z.
cakephp phpunit cakephp-3.0 phpunit-testing
asked Mar 27 at 14:39
ZenzsZenzs
539 bronze badges
add a comment |
A couple of days ago I upgraded my app from 3.6.6 to 3.7.5. Before I did the upgrade I ran all my tests which provided the following results:
// Environment
CakePHP Version: 3.6.6
PHPUnit Version: 6.5.14
// Results
Tests: 476, Assertions: 1927
// Sublime Text 3 find with $this->assert
1038 $this->assert's found.
Therefore: 1038 $this->assert found and 1927 assertions in results.
// Controller Test
use CakeTestSuiteIntegrationTestCase;
class UsersControllerTest extends IntegrationTestCase
{
======================================================================
I created a new project with composer self-update && composer create-project --prefer-dist cakephp/app app_name.
I copied all the files over and implemented the changes documented in the migration guide.
I logged in and everything worked (Except for the middleware csrf token mismatch error but thats another issue.)
I ran my tests again and the following results where provided.
// Environment
CakePHP Version: 3.7.5
PHPUnit Version: 6.5.8
// Results
Tests: 497, Assertions: 1135
// Sublime Text 3 find with $this->assert
1059 $this->assert's found.
Therefore: 1059 $this->assert found and 1135 assertions in results.
// Controller Test
use CakeTestSuiteTestCase;
use CakeTestSuiteIntegrationTestTrait;
class UsersControllerTest extends TestCase
{
use IntegrationTestTrait;
======================================================================
I've double checked I copied everything over accurately and everything is as it should be apart from understanding
the test results.
I also used Sublime Text 3 to check that I hadn't called $this->assert 792 more times after my upgrade but this confirmed it's been called the correct amount of times taking into consideration I did 21 more tests.
The only differences I can see are:
- In 3.6.6 IntegrationTestCase is used.
In 3.6.6 PHPUnit Version: 6.5.14 is used.
In 3.7.5 TestCase and IntegrationTestTrait is used.
- In 3.7.5 PHPUnit Version: 6.5.8 is used.
======================================================================
// Question:
I'm hoping someone can help me understand why I can do 21 more tests but have 792 less assertions? Is it the use of TestCase and IntegrationTestTrait instead of IntegrationTestCase or the PHPUnit version difference or maybe something else?
Thanks. Z.
======================================================================
@ndm, thanks for the input.
I would like to follow your advice but the situation has changed. I got up this morning and tried to replicate the results from yesterday. My new 3.7.5 app test results were the same:
// Environment
CakePHP Version: 3.7.5
PHPUnit Version: 6.5.8
// Results
Tests: 497, Assertions: 1135
Then I loaded my old 3.6.6 app and ran the tests again but the PHPUnit version had changed and these were the results:
// Environment
CakePHP Version: 3.6.6
PHPUnit Version: 6.5.8
// Results
Tests: 497, Assertions: 1135
I thought I'd made a mistake yesterday and copied the wrong folder so I got my master backups out which hadn't been touched (All the way back to 19/01/19). I loaded 4 backups all on CakePHP version 3.6.6. All of them show these results.
// Environment
CakePHP Version: 3.6.6
PHPUnit Version: 6.5.8
// Results
Tests: 497, Assertions: 1135
So now I'm wondering where on earth is PHPUnit 6.5.14?
Since 19/01/19 I've run my tests on my CakePHP 3.6.6 apps about 50 times and when you run the test the cmd line always displays the PHPUnit version so I know I was using PHPUnit 6.5.14.
And now I'm wondering what could explain this? This also means I cannot replicate the results from yesterday.
Your advice has put my mind at rest, ie: it could be a lot of different things. Also I need to weigh up the time it would take me to isolate the reason against the benefits of knowing the reason.
For the moment I've decided to put this issue on my to do list seeing as it still does run all the tests and it could be as you mention "Maybe some assertion methods provided by CakePHP changed so that they internally make less calls to PHPUnit assertion methods. Maybe PHPUnit wasn't calculating things incorrectly in earlier versions. Maybe something totally different, there could be lots of reasons" and it's an unknown amount of time to get to the bottom of.
Hopefully within the next couple of months I can free up some time to get into it but for the moment I've filed it under "Sherlock Holmes and the case of the missing PHPUnit version". :)
Thanks again, Z.
cakephp phpunit cakephp-3.0 phpunit-testing
asked Mar 27 at 14:39
ZenzsZenzs
539 bronze badges
Maybe some assertion methods provided by CakePHP changed so that they internally make less calls to PHPUnit assertion methods. Maybe PHPUnit wasn't calculating things incorrectly in earlier versions. Maybe something totally different, there could be lots of reasons, pretty hard for anyone here to tell. You could start with updating PHPUnit and CakePHP separately, and in patch version steps (ie3.6.6>3.6.7>3.6.8etc), to check when exactly the assertion count changes, and then check what exactly changed in between the two releases. Also use a copy of your original app, not a new one.
– ndm
Mar 28 at 11:02
add a comment |
A couple of days ago I upgraded my app from 3.6.6 to 3.7.5. Before I did the upgrade I ran all my tests which provided the following results:
// Environment
CakePHP Version: 3.6.6
PHPUnit Version: 6.5.14
// Results
Tests: 476, Assertions: 1927
// Sublime Text 3 find with $this->assert
1038 $this->assert's found.
Therefore: 1038 $this->assert found and 1927 assertions in results.
// Controller Test
use CakeTestSuiteIntegrationTestCase;
class UsersControllerTest extends IntegrationTestCase
{
======================================================================
I created a new project with composer self-update && composer create-project --prefer-dist cakephp/app app_name.
I copied all the files over and implemented the changes documented in the migration guide.
I logged in and everything worked (Except for the middleware csrf token mismatch error but thats another issue.)
I ran my tests again and the following results where provided.
// Environment
CakePHP Version: 3.7.5
PHPUnit Version: 6.5.8
// Results
Tests: 497, Assertions: 1135
// Sublime Text 3 find with $this->assert
1059 $this->assert's found.
Therefore: 1059 $this->assert found and 1135 assertions in results.
// Controller Test
use CakeTestSuiteTestCase;
use CakeTestSuiteIntegrationTestTrait;
class UsersControllerTest extends TestCase
{
use IntegrationTestTrait;
======================================================================
I've double checked I copied everything over accurately and everything is as it should be apart from understanding
the test results.
I also used Sublime Text 3 to check that I hadn't called $this->assert 792 more times after my upgrade but this confirmed it's been called the correct amount of times taking into consideration I did 21 more tests.
The only differences I can see are:
- In 3.6.6 IntegrationTestCase is used.
In 3.6.6 PHPUnit Version: 6.5.14 is used.
In 3.7.5 TestCase and IntegrationTestTrait is used.
- In 3.7.5 PHPUnit Version: 6.5.8 is used.
======================================================================
// Question:
I'm hoping someone can help me understand why I can do 21 more tests but have 792 less assertions? Is it the use of TestCase and IntegrationTestTrait instead of IntegrationTestCase or the PHPUnit version difference or maybe something else?
Thanks. Z.
======================================================================
@ndm, thanks for the input.
I would like to follow your advice but the situation has changed. I got up this morning and tried to replicate the results from yesterday. My new 3.7.5 app test results were the same:
// Environment
CakePHP Version: 3.7.5
PHPUnit Version: 6.5.8
// Results
Tests: 497, Assertions: 1135
Then I loaded my old 3.6.6 app and ran the tests again but the PHPUnit version had changed and these were the results:
// Environment
CakePHP Version: 3.6.6
PHPUnit Version: 6.5.8
// Results
Tests: 497, Assertions: 1135
I thought I'd made a mistake yesterday and copied the wrong folder so I got my master backups out which hadn't been touched (All the way back to 19/01/19). I loaded 4 backups all on CakePHP version 3.6.6. All of them show these results.
// Environment
CakePHP Version: 3.6.6
PHPUnit Version: 6.5.8
// Results
Tests: 497, Assertions: 1135
So now I'm wondering where on earth is PHPUnit 6.5.14?
Since 19/01/19 I've run my tests on my CakePHP 3.6.6 apps about 50 times and when you run the test the cmd line always displays the PHPUnit version so I know I was using PHPUnit 6.5.14.
And now I'm wondering what could explain this? This also means I cannot replicate the results from yesterday.
Your advice has put my mind at rest, ie: it could be a lot of different things. Also I need to weigh up the time it would take me to isolate the reason against the benefits of knowing the reason.
For the moment I've decided to put this issue on my to do list seeing as it still does run all the tests and it could be as you mention "Maybe some assertion methods provided by CakePHP changed so that they internally make less calls to PHPUnit assertion methods. Maybe PHPUnit wasn't calculating things incorrectly in earlier versions. Maybe something totally different, there could be lots of reasons" and it's an unknown amount of time to get to the bottom of.
Hopefully within the next couple of months I can free up some time to get into it but for the moment I've filed it under "Sherlock Holmes and the case of the missing PHPUnit version". :)
Thanks again, Z.
cakephp phpunit cakephp-3.0 phpunit-testing
asked Mar 27 at 14:39
ZenzsZenzs
539 bronze badges
A couple of days ago I upgraded my app from 3.6.6 to 3.7.5. Before I did the upgrade I ran all my tests which provided the following results:
// Environment
CakePHP Version: 3.6.6
PHPUnit Version: 6.5.14
// Results
Tests: 476, Assertions: 1927
// Sublime Text 3 find with $this->assert
1038 $this->assert's found.
Therefore: 1038 $this->assert found and 1927 assertions in results.
// Controller Test
use CakeTestSuiteIntegrationTestCase;
class UsersControllerTest extends IntegrationTestCase
{
======================================================================
I created a new project with composer self-update && composer create-project --prefer-dist cakephp/app app_name.
I copied all the files over and implemented the changes documented in the migration guide.
I logged in and everything worked (Except for the middleware csrf token mismatch error but thats another issue.)
I ran my tests again and the following results where provided.
// Environment
CakePHP Version: 3.7.5
PHPUnit Version: 6.5.8
// Results
Tests: 497, Assertions: 1135
// Sublime Text 3 find with $this->assert
1059 $this->assert's found.
Therefore: 1059 $this->assert found and 1135 assertions in results.
// Controller Test
use CakeTestSuiteTestCase;
use CakeTestSuiteIntegrationTestTrait;
class UsersControllerTest extends TestCase
{
use IntegrationTestTrait;
======================================================================
I've double checked I copied everything over accurately and everything is as it should be apart from understanding
the test results.
I also used Sublime Text 3 to check that I hadn't called $this->assert 792 more times after my upgrade but this confirmed it's been called the correct amount of times taking into consideration I did 21 more tests.
The only differences I can see are:
- In 3.6.6 IntegrationTestCase is used.
In 3.6.6 PHPUnit Version: 6.5.14 is used.
In 3.7.5 TestCase and IntegrationTestTrait is used.
- In 3.7.5 PHPUnit Version: 6.5.8 is used.
======================================================================
// Question:
I'm hoping someone can help me understand why I can do 21 more tests but have 792 less assertions? Is it the use of TestCase and IntegrationTestTrait instead of IntegrationTestCase or the PHPUnit version difference or maybe something else?
Thanks. Z.
======================================================================
@ndm, thanks for the input.
I would like to follow your advice but the situation has changed. I got up this morning and tried to replicate the results from yesterday. My new 3.7.5 app test results were the same:
// Environment
CakePHP Version: 3.7.5
PHPUnit Version: 6.5.8
// Results
Tests: 497, Assertions: 1135
Then I loaded my old 3.6.6 app and ran the tests again but the PHPUnit version had changed and these were the results:
// Environment
CakePHP Version: 3.6.6
PHPUnit Version: 6.5.8
// Results
Tests: 497, Assertions: 1135
I thought I'd made a mistake yesterday and copied the wrong folder so I got my master backups out which hadn't been touched (All the way back to 19/01/19). I loaded 4 backups all on CakePHP version 3.6.6. All of them show these results.
// Environment
CakePHP Version: 3.6.6
PHPUnit Version: 6.5.8
// Results
Tests: 497, Assertions: 1135
So now I'm wondering where on earth is PHPUnit 6.5.14?
Since 19/01/19 I've run my tests on my CakePHP 3.6.6 apps about 50 times and when you run the test the cmd line always displays the PHPUnit version so I know I was using PHPUnit 6.5.14.
And now I'm wondering what could explain this? This also means I cannot replicate the results from yesterday.
Your advice has put my mind at rest, ie: it could be a lot of different things. Also I need to weigh up the time it would take me to isolate the reason against the benefits of knowing the reason.
For the moment I've decided to put this issue on my to do list seeing as it still does run all the tests and it could be as you mention "Maybe some assertion methods provided by CakePHP changed so that they internally make less calls to PHPUnit assertion methods. Maybe PHPUnit wasn't calculating things incorrectly in earlier versions. Maybe something totally different, there could be lots of reasons" and it's an unknown amount of time to get to the bottom of.
Hopefully within the next couple of months I can free up some time to get into it but for the moment I've filed it under "Sherlock Holmes and the case of the missing PHPUnit version". :)
Thanks again, Z.
cakephp phpunit cakephp-3.0 phpunit-testing
cakephp phpunit cakephp-3.0 phpunit-testing
asked Mar 27 at 14:39
ZenzsZenzs
539 bronze badges
asked Mar 27 at 14:39
ZenzsZenzs
539 bronze badges
edited Mar 28 at 12:45
Zenzs
asked Mar 27 at 14:39
ZenzsZenzs
539 bronze badges
asked Mar 27 at 14:39
ZenzsZenzs
539 bronze badges
asked Mar 27 at 14:39
ZenzsZenzs
539 bronze badges
539 bronze badges
Maybe some assertion methods provided by CakePHP changed so that they internally make less calls to PHPUnit assertion methods. Maybe PHPUnit wasn't calculating things incorrectly in earlier versions. Maybe something totally different, there could be lots of reasons, pretty hard for anyone here to tell. You could start with updating PHPUnit and CakePHP separately, and in patch version steps (ie3.6.6>3.6.7>3.6.8etc), to check when exactly the assertion count changes, and then check what exactly changed in between the two releases. Also use a copy of your original app, not a new one.
– ndm
Mar 28 at 11:02
add a comment |
Maybe some assertion methods provided by CakePHP changed so that they internally make less calls to PHPUnit assertion methods. Maybe PHPUnit wasn't calculating things incorrectly in earlier versions. Maybe something totally different, there could be lots of reasons, pretty hard for anyone here to tell. You could start with updating PHPUnit and CakePHP separately, and in patch version steps (ie3.6.6>3.6.7>3.6.8etc), to check when exactly the assertion count changes, and then check what exactly changed in between the two releases. Also use a copy of your original app, not a new one.
– ndm
Mar 28 at 11:02
Maybe some assertion methods provided by CakePHP changed so that they internally make less calls to PHPUnit assertion methods. Maybe PHPUnit wasn't calculating things incorrectly in earlier versions. Maybe something totally different, there could be lots of reasons, pretty hard for anyone here to tell. You could start with updating PHPUnit and CakePHP separately, and in patch version steps (ie
3.6.6 > 3.6.7 > 3.6.8 etc), to check when exactly the assertion count changes, and then check what exactly changed in between the two releases. Also use a copy of your original app, not a new one.– ndm
Mar 28 at 11:02
Maybe some assertion methods provided by CakePHP changed so that they internally make less calls to PHPUnit assertion methods. Maybe PHPUnit wasn't calculating things incorrectly in earlier versions. Maybe something totally different, there could be lots of reasons, pretty hard for anyone here to tell. You could start with updating PHPUnit and CakePHP separately, and in patch version steps (ie
3.6.6 > 3.6.7 > 3.6.8 etc), to check when exactly the assertion count changes, and then check what exactly changed in between the two releases. Also use a copy of your original app, not a new one.– ndm
Mar 28 at 11:02
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55379927%2fphpunit-test-assertions-different-after-upgrade-from-3-6-6-to-3-7-5%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Is this question similar to what you get asked at work? Learn more about asking and sharing private information with your coworkers using Stack Overflow for Teams.
Is this question similar to what you get asked at work? Learn more about asking and sharing private information with your coworkers using Stack Overflow for Teams.
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55379927%2fphpunit-test-assertions-different-after-upgrade-from-3-6-6-to-3-7-5%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Maybe some assertion methods provided by CakePHP changed so that they internally make less calls to PHPUnit assertion methods. Maybe PHPUnit wasn't calculating things incorrectly in earlier versions. Maybe something totally different, there could be lots of reasons, pretty hard for anyone here to tell. You could start with updating PHPUnit and CakePHP separately, and in patch version steps (ie
3.6.6>3.6.7>3.6.8etc), to check when exactly the assertion count changes, and then check what exactly changed in between the two releases. Also use a copy of your original app, not a new one.– ndm
Mar 28 at 11:02