This repository was archived by the owner on Mar 12, 2025. It is now read-only.
Use stdout stream for reports when available #97
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 2 commits
October 19, 2021 13:12
Use stdout stream for reports when available. This avoids "Headers already sent" types of issues, when manipulating a session during testing.
The constant is defined as fopen('php://stdout', 'w'), not php://stdout.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Use stdout stream for reports when available. This avoids "Headers already sent" types of issues, when manipulating a session during testing.
When manipulating headers during acceptance testing, those tests would fail, if a report with output was activated. This could be the situation if running Codeception tests from PHPStorm.
A workaround is to use ob_start() in a bootstrap as described here https://stackoverflow.com/questions/31175636/headers-already-sent-running-unit-tests-in-phpstorm and here https://intellij-support.jetbrains.com/hc/en-us/community/posts/360000404160-Codeception-test-reports-Headers-already-sent-in-vendor-phpunit-phpunit-src-Util-Printer-php-on-line-109.
Using ob_start(), the user has to wait for all tests to complete, before the report-output is available.