+ tests

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

and restore Transitions tests which I deleted by mistake earlier

refs #3913 Fixes API for dashboards + disabling Dashboard API tests for now

 * 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!

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

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

refs #1454 new action metrics are only accessed by actions plugin, bounce rate fix, changed color of second line chart series, updated expected test files

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

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

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

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

 * Implementing Custom Date range in Core, eg "period=range&date=2010-01-05,2010-02-03"
 * Only the requested plugin's report will be processed, ensuring fast responses
 * when a large period is requested, the code will try and select an optimal number of sub periods (see Range.test.php) - a mix of weeks, months and days inside the requested range
 * adding integration testing + unit test for optimal subperiods algorithm

TODO
 * we should also use Yearly archives whenever possible (when date range is very large)
 * if custom date range start date == website creation date or before, can use more optimal subperiods (using starting month / year / week)
 * Test/implement "last N days" 
 * Test with timezones when the custom date range ends today
 * UI to allow selecting custom range (show 2 calendars)
 * Update API reference doc + add example in API page listing
 * Add "last 7 days", "last 30 days" in the user settings for "Default date to load"
 
NB: 3 tests fail in Main.test.php on my box, but I'm really not sure why... let's see if Jenkins fails as well

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