summaryrefslogtreecommitdiffstats
path: root/ash/test/ash_test_helper.cc
Commit message (Collapse)AuthorAgeFilesLines
* Use override redirect window for unit testsoshima@chromium.org2013-05-181-0/+7
| | | | | | | | | | | | This is how ash works on the device (no wm) and eliminates flaky-ness caused by WM. BUG=none TEST=none Review URL: https://chromiumcodereview.appspot.com/14698005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@200976 0039d316-1c4b-4281-b951-d872f2087c98
* Move TrayPower related code frome ash/system/power to ↵jennyz@chromium.org2013-05-161-0/+3
| | | | | | | | | | | | | | | | | | | ash/system/chromeos/power. This helps: 1. Remove the duplicated PowerSupplyStatus from ash/system/power. 2. Remove PowerStatusObserver from ash/system/power. 3. Remove power supply status related state, apis and observer from ash_system_tray_delegate.cc. Not done yet: There are still other PowerManagerClient calls in ash_system_tray_delegate.cc, which are used by other code. We may be able to move them into the new PowerManagerHandler, which will further downsize ash_system_tray_delegate. This could be done in another cl. BUG=190299 TBR=sky Review URL: https://chromiumcodereview.appspot.com/14691011 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@200463 0039d316-1c4b-4281-b951-d872f2087c98
* Remove ENABLE_MESSAGE_CENTERdimich@chromium.org2013-05-141-7/+0
| | | | | | | | | | | | | | | | | | Next step on re-factoring Notifications. This will bring the MessageCenter classes, most important message_center::Notification, into build on all systems, including those where the MessageCenter is not yet appearign in UI. This will allow to start using this Notification class in client code and remove the old Notification class defined in chrome/browser/notificaitons/notification.h That will allow the clients that already use Rich Notifications to use richer data type support, for example supply an image bits for a Notification (as in Snapshot notifications). This also removes a lot of compile-time @ifdefs and replaces them with checking a runtime flag which we already have anyways. On Android and iOS, the MessageCenter is not compiled in, for the size concerns and uncertain story for notifications in general - the existing ENABLE_NOTIFICATIONS define is used for that. BUG=174164 Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=199625 Review URL: https://chromiumcodereview.appspot.com/15025002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@199920 0039d316-1c4b-4281-b951-d872f2087c98
* Initialize CrasAudioHandler for testing in ash_unittests and ash_shell ↵jennyz@chromium.org2013-05-131-6/+18
| | | | | | | | | | | startup cases. BUG=237513 R=jamescook@chromium.org, xiyuan@chromium.org Review URL: https://codereview.chromium.org/14757010 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@199757 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 199625 "Remove ENABLE_MESSAGE_CENTER"thakis@chromium.org2013-05-121-0/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | Caused a static initializer on Linux: # message_center_constants.cc __i686.get_pc_thunk.cx (Not on Mac though. The SkGetColor() macro has a comment about it not adding a static initializer on release builds, so maybe it's the float-int-multiplication? I don't have a linux box around to check, sorry.) > Remove ENABLE_MESSAGE_CENTER > > Next step on re-factoring Notifications. This will bring the MessageCenter classes, most important message_center::Notification, into build on all systems, including those where the MessageCenter is not yet appearign in UI. This will allow to start using this Notification class in client code and remove the old Notification class defined in chrome/browser/notificaitons/notification.h > > That will allow the clients that already use Rich Notifications to use richer data type support, for example supply an image bits for a Notification (as in Snapshot notifications). > > This also removes a lot of compile-time @ifdefs and replaces them with checking a runtime flag which we already have anyways. > > On Android and iOS, the MessageCenter is not compiled in, for the size concerns and uncertain story for notifications in general - the existing ENABLE_NOTIFICATIONS define is used for that. > > BUG=174164 > > Review URL: https://chromiumcodereview.appspot.com/15025002 TBR=dimich@chromium.org Review URL: https://codereview.chromium.org/14631021 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@199639 0039d316-1c4b-4281-b951-d872f2087c98
* Remove ENABLE_MESSAGE_CENTERdimich@chromium.org2013-05-111-8/+0
| | | | | | | | | | | | | | | | Next step on re-factoring Notifications. This will bring the MessageCenter classes, most important message_center::Notification, into build on all systems, including those where the MessageCenter is not yet appearign in UI. This will allow to start using this Notification class in client code and remove the old Notification class defined in chrome/browser/notificaitons/notification.h That will allow the clients that already use Rich Notifications to use richer data type support, for example supply an image bits for a Notification (as in Snapshot notifications). This also removes a lot of compile-time @ifdefs and replaces them with checking a runtime flag which we already have anyways. On Android and iOS, the MessageCenter is not compiled in, for the size concerns and uncertain story for notifications in general - the existing ENABLE_NOTIFICATIONS define is used for that. BUG=174164 Review URL: https://chromiumcodereview.appspot.com/15025002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@199625 0039d316-1c4b-4281-b951-d872f2087c98
* Move Ash window-show code from AshTestHelper back to AshTestBasejamescook@chromium.org2013-05-021-63/+0
| | | | | | | | | | | | | | | This allows other tests (Chrome OS BrowserWithTestWindowTest in particular) to use AshTestHelper without opening an X window. This speeds up the tests noticably and makes them less flaky when running locally. This is a partial revert of https://chromiumcodereview.appspot.com/14284017/ - I was too aggressive in moving code from AshTestBase to AshTestHelper. BUG=233374 TEST=ash_unittests, unit_tests Review URL: https://chromiumcodereview.appspot.com/14791002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@197924 0039d316-1c4b-4281-b951-d872f2087c98
* cros: Enable new cras audio handler by default rkc@chromium.org2013-05-011-0/+4
| | | | | | | | | | | | | | | Add separate flag for audio device switcher menu, off by default. Picking this up from https://codereview.chromium.org/14455012/; only fixed tests. R=jamescook@chromium.org TBR=stevenjb@chromium.org,jennyz@chromium.org BUG=160311 TEST=Audio input/output/mute still works Review URL: https://chromiumcodereview.appspot.com/14678004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@197644 0039d316-1c4b-4281-b951-d872f2087c98
* Add AshTestHelper to let unit tests create windows on Ashjamescook@chromium.org2013-04-261-0/+152
BUG=235474,233374 TEST=ash_unittests, unit_tests Review URL: https://chromiumcodereview.appspot.com/14284017 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@196652 0039d316-1c4b-4281-b951-d872f2087c98
generated by cgit v1.1 at 2025-02-06 01:44:46 +0000