Skip to content
This repository was archived by the owner on Apr 12, 2018. It is now read-only.

Upgrading from PHPUnit 3.7 to PHPUnit 4.0 page misses folder structure change #244

Closed
gmazzap opened this issue Dec 12, 2014 · 1 comment

Comments

@gmazzap
Copy link

gmazzap commented Dec 12, 2014

I'm upgrading some tests wrote for PHPUnit 3.7 to 4.4.

After updating I got an error because in my bootstrap file I was requiring

/vendor/phpunit/phpunit/PHPUnit/Framework/Assert/Functions.php

but with version 4 this folder structure is no longer valid, because now base folder for framework is src and not PHPUnit, so the correct path now is:

/vendor/phpunit/phpunit/src/Framework/Assert/Functions.php

I think that the folder structure change should be mentioned in the "Upgrading from PHPUnit 3.7 to PHPUnit 4.0" documentation page.

@sebastianbergmann
Copy link
Owner

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/.

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).

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants