“headers already sent” Error returned during PHPUnit tests

安稳与你 提交于 2019-12-04 03:51:39
Fabian Schmengler

There are several options with different advantages and disadvantages:

  1. run the tests in separate processes with @runInSeparateProcess, as you already found out. Good: better test isolation, Bad: worse performance, does not work well with global constants
  2. use --stderr flag to direct PHPUnit output to STDERR. Good: tests work as expected without changes, Bad: feels like a dirty workaround, possibly problems with CI tools
  3. don't actually send headers. Either replace the classes that use header() with stubs or if this is not easily possible or you want to do a full functional test, mock the header() function itself. More info on mocking built-in functions in this answer. Good: you can test the contents of the headers as well, your tests do rely less on global state Bad: You'll need to write more test code

I'd go for (3) and probably refactor the code as well to have a single class that's responsible for the headers and can be easily mocked.

易学教程内所有资源均来自网络或用户发布的内容,如有违反法律规定的内容欢迎反馈
该文章没有解决你所遇到的问题?点击提问,说说你的问题,让更多的人一起探讨吧!