Skip to content
This repository has been archived by the owner on Jan 25, 2022. It is now read-only.

Implement PHPUnit as a (PHP) ScriptComponent #25

Open
andreasnrb opened this issue Apr 11, 2016 · 7 comments
Open

Implement PHPUnit as a (PHP) ScriptComponent #25

andreasnrb opened this issue Apr 11, 2016 · 7 comments
Assignees
Labels
Component Service, Executable, Script, Source or Data Packages to extend WPLib Box (Previously "Installable") To Discuss
Milestone

Comments

@andreasnrb
Copy link
Contributor

Since you need to run phpunit in the VM for the WP integration test to work adding it either to box or during provision would be good. If provision probably some check if installed should be added so it doesn't get redownloaded or anything like that unless there is update.

@mikeschinkel mikeschinkel added this to the Future milestone Apr 12, 2016
@mikeschinkel
Copy link
Member

@andreasnrb Can you give more details about exactly what you would like here?

@andreasnrb
Copy link
Contributor Author

Well just that phpunit is installed globally on provision probably using
Composer. Which version is to be used I'm not sure. I just use the latest
personally. PHPUnit by default or not is probably a personal dev choice
though. Might be a thing people add on their own to Composer if/when they
fork the wplib repo?

2016-04-12 4:02 GMT+02:00 Mike Schinkel notifications@github.com:

@andreasnrb https://github.com/andreasnrb Can you give more details
about exactly what you would like here?


You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#25 (comment)

@clubdeuce
Copy link
Contributor

I think this should be left to the individual developer.

@mikeschinkel
Copy link
Member

I am still open to the idea, but I'd like to hear from 5 or 10 other developers to see what they think and how they think having it in the box vs. just installing on the host/developer's machine would be useful.

@mikeschinkel
Copy link
Member

So @clubdeuce and I discussed this and we came up with the following:

  1. PHPUnit should be installed per project using Composer to ensure project-level compatibility,
  2. However, WPLib Box should run unit tests on Git commit, and
  3. Our future command line tool should allow invoking PHP to run inside WPLib Box (the guest) and allow for output on the developer's command line (the host's command line).

We wanted to run this by everyone here and has out the requirements to make sure we have them right before we go to implement them.

@mikeschinkel
Copy link
Member

@MickMakes I am revisiting this.

PHPUnit is something WPLib Box should make trivially easy. We should also make it possible to use with PhpStorm on a host machine to debug unit testing run from within the box, if at all possible (not sure, but this might help.)

@mikeschinkel
Copy link
Member

The PHPUnit site includes the different versions of PHPUnit and which versions or PHP they work with, currently:

Major Version PHP Compatibility Initial Release Support
PHPUnit 8 PHP 7.2, PHP 7.3, PHP 7.4 Feb 1, 2019 Support ends on Feb 5, 2021
PHPUnit 7 PHP 7.1, PHP 7.2, PHP 7.3 Feb 2, 2018 Support ends on Feb 7, 2020
PHPUnit 6 PHP 7.0, PHP 7.1, PHP 7.2 Feb 3, 2017 Support ends on Feb 1, 2019
PHPUnit 5 PHP 5.6, PHP 7.0, PHP 7.1 Oct 2, 2015 Support ended on Feb 2, 2018

@mikeschinkel mikeschinkel changed the title Add phpunit Implement PHPUnit as a (PHP) ScriptComponent Jul 24, 2018
@mikeschinkel mikeschinkel self-assigned this Jul 24, 2018
@mikeschinkel mikeschinkel added To Discuss Component Service, Executable, Script, Source or Data Packages to extend WPLib Box (Previously "Installable") and removed Feature labels Jul 24, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Component Service, Executable, Script, Source or Data Packages to extend WPLib Box (Previously "Installable") To Discuss
Projects
None yet
Development

No branches or pull requests

4 participants