Refactor API.getSegmentsMetadata and Plugin\Segment so segments are all defined through Plugin\Segment class in dimensions & make sure AutoSuggestAPITest data providers do not use database.

Fixing two more system test failures, including one caused by the static cache in Archive.php never being cleared, and the environment not existing in web archiving.

Refresh the Cache in tests so that custom variable max slot\ is properly initialised, and all segments are found

refs #5940 moved files into a subfolder framework, added autoloader to remove duplicated code to load autoload.php and to be able to register more autoloaders (eg for test files) on demand. This I got read of many includes that had to be updated all the time and that had to be updated all the time when moving iles

refs #5940 we might stay backwards compatible this way for 2 months. moved some tests from unit to integration and explained when a test is a unit test, an integration test or a system test.

refs #5940 put tests in correct folders, better testsuite names, some tests still fail and I cannot figure out why

Refs #5800, add namespaces to integration tests in root folder. Also add IntegrationTestCase to a namespace, re-add individual test @groups, move test groups to class level, and rename test files & class names so underscores are not used.

Piwik is a free/libre analytics platform. Refs #4455 GNU Package requirement to use free/libre instead of open source

- Rename *_BaseFixture to Fixture.
- Move DB setup code to Fixture and reuse code in DatabaseTestCase.
- Make IntegrationTestCase::$defaultApiNotToCall an instance var.

Added namespaces to functions.php files in the five plugins that had one
Work in progress

 * new segment 'siteSearchKeyword'
Fixes #3903, #3905:
 * adding few fields in the Live API output to accomodate getSuggestedValuesForSegment
 * renamed other fields for consistency with segment names
Fixes #3906:
 * new API: getSuggestedValuesForSegment which returns top suggested values for a particular segment. It uses the Live.getLastVisitsDetails API to fetch the most recently used values, and will show the most used values first

 * Adding tests for everything. The test case actually generates data for all segments so that VisitsSummary.get returns some data for each of the 47 segments being tested returns some data.
  How it works:
  * generate extended data in fixture
  * Tests (1) call getSuggestedValuesForSegment for each segment, check there is some data returned for each segment
  * get the first suggested value from the list,
  * Tests (2) call VisitsSummary.get with this segment value, eg. countryCode==ru.
    * I worked this way for all 47 segments until all tests had some data ==> now we know that all segments have been tested and that the auto suggest works for all segments. TDD FTW!

Converting Piwik core source files, PHP, JS, TPL, CSS

More info: http://piwik.org/participate/coding-standards/

Refs #2908, refactored tests so database setup (adding sites, tracking visits) are separated from API tests. Put setup code into fixtures and reused code as much as possible.

refs #3227 removed class inheritance as that causes problems in some tests. improved and fixed some tests. now even more tests are running

git-svn-id: http://dev.piwik.org/svn/trunk@6676 59fd770c-687e-43c8-a1e3-f5a4ff64c105

while setup (atm bulk tracking doesn't work)


git-svn-id: http://dev.piwik.org/svn/trunk@6645 59fd770c-687e-43c8-a1e3-f5a4ff64c105

refs #3227 refactored integration tests to setup database and tracking only once per class; that should speed up the tests a bit

git-svn-id: http://dev.piwik.org/svn/trunk@6626 59fd770c-687e-43c8-a1e3-f5a4ff64c105

git-svn-id: http://dev.piwik.org/svn/trunk@6597 59fd770c-687e-43c8-a1e3-f5a4ff64c105