![Popular open source software is more secure than unpopular open source software, because insecure software becomes unpopular fast. [That doesn't happen for proprietary software.]](../sites/all/themes/drupal4hu/images/bg-center/bg-center_4.png)
I thought this evident but apparently not. You can download Drupal and run the tests provided. Just like that. If you download a few contribs and they have tests you still can run tests on any webserver, any environment what so ever to see whether they work together. It can be a small host or a cloud provider where all you have is the browser and no command line.
And let me note that I love being able to access the Drupal API while testing Drupal.
Commenting on this Story is closed.
You can still use the Drupal API in tests. If you couldn't, how else could all the existing tests be passing in Upal? See DrupalUnitTestCase at https://github.com/weitzman/upal/blob/master/drupal_test_case.php#L2320.
There are always benefits and risks with major changes like this. You have to sum up both sides and see which way the scale tips for you. I will note that the standard practice in PHP and even other languages is to include the tests in the project but not the test runner. I think Drupal is quite non-standard in this regard.
BTW, Jimmy is on board with this plan, and even wants to go further - http://blog.boombatower.com/testing-battle-plan
this is moshe speaking, BTW.