Note that there are some explanatory texts on larger screens.

plurals
  1. PORun PHPUnit without shell access to my php server
    primarykey
    data
    text
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. COI know that PHPStorm IDE offers a feature to run Unit-Tests on your server: http://www.jetbrains.com/phpstorm/webhelp/run-debug-configuration-phpunit-on-server.html - But for a distinct setup - like for testing - you always have some work. Alternatively if you've got SSH access to your host, you can also just run it in CLI. I normally won't call that too many requirements. But probably you're just a bit complaining because you don't get it to run? I can hardly imagine it was a better situation years ago. The alternative is to test in your dev environment.
      singulars
    2. COYou'd be surprised. PHPUnit used to include a pure php runner. Most of the hosting my students end up with, dont allow for any shell (or SSH) access, and therefore can not run Pear. So requiring either shell access or pear locks them totally out
      singulars
    3. COI think there still is a webinterface for PHPUnit. And the testrunner itself still is in PHP. And instead of pear you can package phpunit with composer so you can configure the software on your system and then upload to the server. So the requirements you give seem a little bit misleading to me, even if the servers capabilities are limited, as long as you can upload files and the server exectutes PHP, there is nothing that prevents running the tests remotely I'd say. I'd say it would be a good task to get that to run for your students. A good excercise.
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload