fixed notice

Allow extra environments to be specified through testing environment variables, add a new one for UI tests call ui-test.php, use to remove port from localhost in UI tests, and fix a bug in ContainerFactory (config/config.php should be applied after environment files).

Add event that allows plugins to archive data even if there are no visits for the period. Undocumented for now.

In SystemTestCase, override testing environment var using new Fixture property instead of through DI, so the change is reflected in child processes.

Make sure dbName testing environment variable is set properly in Fixture.php so UI tests w/ --persist-fixture-data will work correctly.

Setup test environment before anything else in Fixture setup so test case class and fixture class show up properly.

Add parameter docs specifying that parameters are ignored for Fixture::loadAllPlugins. For users that want to use the method.

Make sure provideContainerConfig() results in Fixture are propagated to all PHP child processes during tests.

Load plugins in tests automatically through testing environment manipulation, instead of through a method in Fixture. Allows plugin environment configs to be loaded during tests.

Make sure test case class is saved in TestingEnvironment file so proxy entry points will apply overridden DI config.

Rename Piwik_TestingEnvironment to TestingEnvironment and move the class to Piwik\Tests\Framework namespace. Remove manual require statements.

Moved Config object to the DI container and override w/ TestConfig through DI config. Replaced the singleton GlobalSettingsProvider hack w/ the concept of an EnvironmentManipulator (internal to Piwik, not to be used anywhere but TestingEnvironment.php).

Make sure custom container config defined in Fixtures w/ provideContainerConfig override is applied when creating the Environment. Also allow SystemTestCases and IntegrationTestCases to override container config from the test class, without creating a custom Fixture.

For integration tests, recreate test environment in setUp(). This is required since the environment can be modified during tests, and these modifications must be removed after (eg, event observers can be registered). Since Plugin\Manager is in DI, we must also reload plugins.

Integration/Plugin/ManagerTest.php was modified; order of plugins changed because Fixture::loadPlugins() will use TestingEnvironment to gather plugins, which sorts plugins by name.

Use observers.global DI config in TestingEnvironment to define event observers, since the container is not created at this point.