aboutsummaryrefslogtreecommitdiff
path: root/tests
Commit message (Collapse)AuthorAgeFilesLines
* Include <functional> to fix a build issues with g++7.Andrea Azzarone2017-10-231-0/+1
|
* Fork from Ubuntu's indicator-sound.Mike Gabriel2017-10-2210-133/+140
|
* Add comment explaining pulseaudio startup issue.Rodney Dawes2017-03-281-0/+7
|
* Fix cmake option.Rodney Dawes2017-03-271-1/+1
|
* Disable integration tests when running under jenkins environment for now.Rodney Dawes2017-03-271-2/+10
|
* Use coverage support from cmake-extras.Rodney Dawes2017-02-072-0/+21
|
* Use only the gmock module from cmake-extras.Rodney Dawes2017-02-072-23/+10
|
* Fix gmock breakagePete Woods2016-12-091-2/+2
|
* Added volume check to root icon testXavi Garcia Mena2016-03-171-0/+22
|
* Changed code to get root icon, tests addedXavi Garcia Mena2016-03-163-0/+85
|
* Add changes to show up the microphone controls when an external microphone ↵Xavi Garcia Mena2016-03-073-20/+250
|\ | | | | | | | | | | is detected. Approved by: PS Jenkins bot, Charles Kerr
| * Added integration tests to detect external microphonesXavi Garcia Mena2016-03-043-20/+250
| |
* | To avoid going too below the warning level we set the volume when showing ↵Xavi Garcia Mena2016-03-071-1/+1
|\ \ | |/ |/| | | | | | | | | | | | | | | | | | | | | the warning dialog to the loud_volume level. The spec states: Whenever you increase volume, for the first time in 20 hours, such that acoustic output would be more than 85 dBA, an “Increase Volume” dialog should appear. So the loud_volume is still a valid level. After setting this the user has only to press the Up button once to show the warning dialog again. When setting the loud_volume-1 value the level was decreased 2 steps below the warning level and the used had to press the up button twice. Approved by: PS Jenkins bot, Charles Kerr
| * Set warning volume to the maximum allowed when the user presses cancelXavi Garcia Mena2016-03-011-1/+1
| |
* | Changed following Charles's suggestionsXavi Garcia Mena2016-03-022-8/+8
|/
* Fixed integration testXavi Garcia Mena2016-02-231-2/+0
|
* Created new class AccountsServiceAccess to hold all accounts service operationsXavi Garcia Mena2016-02-232-610/+621
|
* added integration test to check last running playerXavi Garcia Mena2016-02-235-11/+87
|
* Changed last running player to user Accounts serviceXavi Garcia Mena2016-02-223-19/+50
|
* Added persistence for last running playerXavi Garcia Mena2016-02-102-4/+3
|
* Fixed tabsXavi Garcia Mena2016-02-041-5/+4
|
* Added Charles suggestionsXavi Garcia Mena2016-02-041-3/+33
|
* added integration tests for adding/removing players and playback controlsXavi Garcia Mena2016-01-296-19/+659
|
* in tests' PulseAudio mock, add pa_context_get_sink_input_info_list() ↵Charles Kerr2016-01-131-0/+19
| | | | implementation
* disable integration test PhoneChangeRoleVolume, amd64 failure seems ↵Charles Kerr2016-01-131-1/+1
| | | | unrelated to these changes & needs fixing in separate MP
* in the integration tests, clamp the random volume selection to a range that ↵Charles Kerr2016-01-121-6/+6
| | | | won't cause the loud-volume-warning code to interfere with the test
* re-enable notifications-testCharles Kerr2016-01-061-1/+1
|
* sync with trunk.15.10Charles Kerr2016-01-061-1/+1
|\
* | in notifications-test, make the loop test more flexiblecharles kerr2016-01-011-16/+27
| |
* | use a custom timer to speed up TriggerWarning's many test combinationscharles kerr2015-12-311-2/+28
| |
* | expand volume warning test to include all trigger requirementscharles kerr2015-12-311-31/+74
| |
* | re-add notifications-test to testscharles kerr2015-12-311-1/+1
| |
* | rename VolumeWarning.high_volume_approved as VolumeWarning.approvedcharles kerr2015-12-312-3/+3
| | | | | | | | | | | | After being moved into a class named "VolumeWarning", the high_volume_ prefix was redunant.
* | add new Notifications test for volume-warning requiring headphonescharles kerr2015-12-301-0/+59
| |
* | in mock Notify server, support actions required for volume warningscharles kerr2015-12-301-1/+1
| |
* | fill out volume-warning-mock's mocking capabilitiescharles kerr2015-12-301-1/+9
| |
* | make VolumeControl::active_output easier to mock for testscharles kerr2015-12-301-1/+11
| |
* | fix and re-enable NotificationsTest::ExtendendVolumeNotificationcharles kerr2015-12-301-3/+4
| |
* | simplify the Options class' propertiescharles kerr2015-12-301-22/+3
| |
* | break volume-warning into an abstract base and concrete pulse-based implcharles kerr2015-12-292-1/+7
| |
* | always keep volume-control's 'stream' property updatedcharles kerr2015-12-202-6/+5
| |
* | change volume-warning to subclass from object instead of volume-controlcharles kerr2015-12-202-0/+75
| | | | | | | | | | Now we're starting to get somewhere...
* | remove 'high_volume' property from volume-controlcharles kerr2015-12-192-7/+3
| |
* | remove 'ready' property from volume-warningcharles kerr2015-12-191-1/+1
| |
* | remove 'is-playing' property from volume-warningcharles kerr2015-12-191-2/+1
| |
* | bugfix: ensure integration tests work regardless of com.ubuntu.sound ↵charles kerr2015-12-193-3/+24
| | | | | | | | gsettings' values
* | instantiate volume-warning and pass it to the servicecharles kerr2015-12-192-10/+35
| |
* | move max_volume into a reusable 'options' classcharles kerr2015-12-194-21/+49
|/
* Disable notification tests that are already covered in the integration tests ↵Xavi Garcia Mena2015-12-181-2/+2
| | | | and fail on amd64
* Added workaround for Maroon in Trouble, second optionXavi Garcia Mena2015-12-171-8/+7
|
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-29 09:12:23 +0000