Use assertSame() instead of assertEquals() where possible

[mhujer]

I noticed that the introductory documentation chapter uses assertEquals(). I suggest that it can be replaced with assertSame(), which is stricter a may prevent unexpected type conversion bugs.

What do you think?

If you think it is a good idea, I can prepare a PR.

[sebastianbergmann]

Dear contributor,

thanks to the hard work by @belanur, @starikovm, @trueromio, and others, the changes outlined in #471 (comment) have been implemented.

This repository, https://github.com/sebastianbergmann/phpunit-documentation, is now archived and read-only. The documentation for PHPUnit version prior to PHPUnit 7.0 will no longer be changed or updated. It is still hosted at

• Multiple HTML files: https://phpunit.de/manual/6.5/en/index.html
• Multiple HTML files (in a .tar.bz2 archive): https://phpunit.de/manual/current/en/download.tar.bz2
• Single HTML file: https://phpunit.de/manual/current/en/phpunit-book.html
• PDF: https://phpunit.de/manual/current/en/phpunit-book.pdf
• ePub: https://phpunit.de/manual/current/en/phpunit-book.epub

Simply replace 6.5 with the version number you are looking for. Simply replace en with fr, pt_br, ja, or zh_cn to access the French, Brazilian Portuguese, Japanese, or Simplified Chinese translation, respectively.

Starting with the documentation for PHPUnit 7.0, the PHPUnit documentation is hosted at https://phpunit.readthedocs.io/.

• The English documentation for PHPUnit is now maintained in the phpunit-documentation-english project
• The French documentation for PHPUnit is now maintained in the phpunit-documentation-french project
• The Brazilian Portuguese documentation for PHPUnit is now maintained in the phpunit-documentation-brazilian-portuguese project
• The Japanese documentation for PHPUnit is now maintained in the phpunit-documentation-japanese project
• The Simplified Chinese documentation for PHPUnit is now maintained in the phpunit-documentation-chinese project

I am sorry that I have to close this issue here as GitHub does not support moving issues from one project to another. Please open a new ticket for this issue in one of the new issue trackers (see above).