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

Before it was loading everything from plugins/* directory, causing tests to fail when tests plugins are there.

Converting Access & Auth to namespace

Notice that auto refactoring has created a nested namespace. Not sure this is what we want - so we might have to edit those nested namespaces afterwards (I think they don't look so good)

Notice that auto refactoring has created a nested namespace. Not sure this is what we want - so we might have to edit those nested namespaces afterwards (I think they don't look so good)

Make Piwik_Access a singleton instance and remove use of Zend_Registry for the Piwik_Access singleton.

 * making tests pass!
 * enabling DevicesDetection tests, even though DevicesDetection plugin is disabled by default.

 * you can now write browserCode==ff;referrerKeyword!= to select all visitors using firefox and that have a keyword set
 * or you can write referrerKeyword==;browserCode==ff to select all visitors using firefox and that did not have any keyword set
Also fixes #3933

Refs #2135
 * fixing last bugs with segment selector encoding (working on chrome + FF + opera) - I 'hope' it will work on iE...

 * 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 #3227 fixed tests expecting an exception, as current phpunit version doesn't support expecting standard exceptions

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

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