You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
App\Test\TestCase\Controller\PagesControllerTest::testDisplay
Will be resolved by adding Configure::write('debug', true);
This repository does not have pages displayed in production.
App\Test\TestCase\Controller\PagesControllerTest::testCsrfAppliedOk
CSRF protection should be applied in production too.
How about asserting the status is not 403?
The text was updated successfully, but these errors were encountered:
Run testDisplay in debug mode.
Pages in this repo can only be displayed in debug mode.
Do not assert normal responses at testCsrfAppliedOk.
Responses may change by debug mode,
but that is not a concern of this test.
Assert the opposite of testCsrfAppliedError.
Refs cakephp#893
Make testBootstrap run in production mode,
and add a case to test bootstrap in debug mode.
DebugKit should not be added in production,
but should be added in debug mode.
Refs cakephp#893
This is a (multiple allowed):
bug
enhancement
feature-discussion (RFC)
CakePHP Application Skeleton Version: 4.3.1
What you did
'debug' => false
(or remove this and do not setDEBUG
environment variable)What happened
What you expected to happen
No failures.
Testing in production environment is nonsense, but testing production behavior is significant.
Some test cases set debug mode by itself.
app/tests/TestCase/Controller/PagesControllerTest.php
Line 79 in a151dcf
DebugKit should not be added in production.
Added at ec4b498.
This seems test
PHP_SELF
in tests/bootstrap.php, but now it is not required. Set PHP_SELF in the integration test case. cakephp#12076Still need this test?
Will be resolved by adding
Configure::write('debug', true);
This repository does not have pages displayed in production.
CSRF protection should be applied in production too.
How about asserting the status is not 403?
The text was updated successfully, but these errors were encountered: