-
Notifications
You must be signed in to change notification settings - Fork 64
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Multi PHP + Multi Environment + Check all commits #212
base: master
Are you sure you want to change the base?
Conversation
- add the label - test dir is a dir (a tmp one) - no cert validation by default - simple WP by default
- support for labels - read latest commits
The code is not very beauty, but it should work... |
this is a first step to include some documentation inside the project, and not only in the handbook page.
Co-authored-by: Matthias Pfefferle <[email protected]>
Co-authored-by: Matthias Pfefferle <[email protected]>
Co-authored-by: Matthias Pfefferle <[email protected]>
Co-authored-by: Matthias Pfefferle <[email protected]>
Co-authored-by: Matthias Pfefferle <[email protected]>
Co-authored-by: Matthias Pfefferle <[email protected]>
Co-authored-by: Matthias Pfefferle <[email protected]>
- Descriptions in 80 chars columns - Some Yoda fixes - Fix the "tab" vs "space" - Check some "comments" that should not be there (they were because some errors on the developing era)
- Better comments / PHPDoc - Improved code quality (do the same, in a better way) - reduce duplicated code (that's something we didn't care at Cloudfest) - updated the Runner Compatibity with PHP 7.2 (as WordPress is)
- Improved readability - default .env updated from source - other fixes
- better documentation - details on each value at the configuration file - scripts so you can run (and update) the software automatically.
I applied the suggestion @pfefferle did on WordCamp Europe, and reduce a lot of duplicated code that we couldn't do at the Cloudfest Hackathon, mostly on the parts when testing multiple PHP versions. I did some improvements on the documentation, with some scripts so the software (from the main branch) is updated and maintained automatically. I've been doing some tests in my local machine, and on my production server (where I was doing the former tests) and looks like everything is working. On my side, I think everything is in order, and we can approve this and put it available for everyone. |
Running tests in parallel?Running the PHPUnit test suite across 7 different PHP versions is taking a long time in my environment. Is there a way to run the tests in parallel to speed things up? Preparing a new environment for every version necessary?Also, is it necessary to create a completely new environment for each PHP version? So far, I've been running the prepare.php file for the first PHP version, running the tests then report.php then using a script to search and replace the PHP executable in the configuration files before rerunning the tests and reporting again. This approach seemed to work. Copying the environment + Running in parallelI could see that using the same environment for multiple php versions in parallel could cause problems, is it maybe possible to just copy one environment to a different directory and then replace the php version in the config? Since preparing an environment also takes a long time for me. |
This is the Cloudfest Hackathon 2024 PR.
This PR solves:
The test-reporter will be upgraded to comply with these changes.