USE_TEST_PROJECT - Document it. Remove KEEP_TEST_PROJECT, since the use-case...

USE_TEST_PROJECT - Document it. Remove KEEP_TEST_PROJECT, since the use-case is handled equally well by USE_TEST_PROJECT.

README.md

@@ -137,3 +137,16 @@ closesly, set the `DEBUG` variable, as in:
 ```
 [~/src/civicrm-asset-plugin] env DEBUG=2 phpunit
 ```
+
+## Local Dev Harness
+
+What if you want to produce an environment which uses the current plugin
+code - one where you can quickly re-run `composer` commands while
+iterating on code?
+
+You may use any of the integration-tests to initialize a baseline
+environment:
+
+```
+env USE_TEST_PROJECT=$HOME/src/myprj phpunit tests/Integration/DrupalProjectPathsTest.php
+```

tests/Integration/IntegrationTestCase.php

@@ -98,8 +98,8 @@ class IntegrationTestCase extends \PHPUnit\Framework\TestCase {
       chdir(self::$origDir);
       self::$origDir = NULL;
 
-      if (getenv('KEEP_TEST_PROJECT')) {
-        fwrite(STDERR, sprintf("\n\nTest project created (%s): %s\n", __CLASS__, self::$testDir));
+      if (getenv('USE_TEST_PROJECT')) {
+        fwrite(STDERR, sprintf("\n\nTest project location (%s): %s\n", __CLASS__, self::$testDir));
       }
       else {
         self::cleanDir(self::$testDir);