aboutsummaryrefslogtreecommitdiff
path: root/tests
Commit message (Collapse)AuthorAgeFilesLines
* sync with trunk.Charles Kerr2014-08-227-1/+894
|\
| * on the bus, publish the battery's power_level as strings rather than intsCharles Kerr2014-07-241-10/+10
| |
| * in notifier.c, fix potential callchain loop when closing a notificationCharles Kerr2014-07-241-5/+28
| |
| * d'ohCharles Kerr2014-07-241-1/+1
| |
| * in tests/glib-fixture.h, sync with the glib-fixture.h from ↵Charles Kerr2014-07-241-37/+40
| | | | | | | | indicator-transfer, it's got less '#if 0' cruft
| * add manual test case for using the indicator-power-service-cmdline-battery ↵Charles Kerr2014-07-221-0/+17
| | | | | | | | test utility
| * Make the when-does-power-level-change tests work whether or not Ephemeral ↵Charles Kerr2014-07-221-2/+2
| | | | | | | | notifications are being used.
| * add indicator-power-service-cmdline-battery, a manual test utility to test ↵Charles Kerr2014-07-224-0/+318
| | | | | | | | the indicator's behavior when a battery's state changes
| * copyediting: code cleanupCharles Kerr2014-07-221-69/+94
| |
| * add tests for events that change whether or not a 'low battery' notification ↵Charles Kerr2014-07-211-6/+91
| | | | | | | | is being shown
| * add tests to confirm that the DBus object's PowerLevel property changes at ↵Charles Kerr2014-07-211-77/+131
| | | | | | | | the right times (and only at the right times) when the battery is draining
| * copy the dbus-test-runner/dbusmock scaffolding for freedesktop Notifications ↵Charles Kerr2014-07-212-14/+316
| | | | | | | | from the indicator-datetime tests
| * add dbus-test-runner as a build dependency for testsCharles Kerr2014-07-211-1/+6
| |
| * sync with lp:indicator-powerCharles Kerr2014-07-211-1/+1
| |\
| * | add first draft of low battery notificationsCharles Kerr2014-07-162-0/+61
| | |
* | | sync unit tests.Charles Kerr2014-07-291-8/+8
| |/ |/|
* | replace 'std::vector<unsigned>' with 'std::vector<unsigned int>' for readabilityCharles Kerr2014-07-171-1/+1
|/
* replace autoconf/automake with cmakeCharles Kerr2014-07-132-71/+46
|
* fix some compiler warnings generated by clang static analyzerCharles Kerr2014-07-131-2/+2
|
* prefer the 'battery-020-charging' icon to the 'battery-low-charging' one ↵Charles Kerr2014-05-051-5/+10
| | | | because the former is more precise so its icon is more likely to be close to the actual actual battery level.
* sync to lp:indicator-powerCharles Kerr2014-03-251-21/+36
|\
| * when expecting a NULL string, use EXPECT_EQ(NULL, str)Charles Kerr2014-03-131-5/+17
| |
| * in the new indicator_power_device_get_*() functions, use heap-allocated ↵Charles Kerr2014-03-131-21/+24
| | | | | | | | strings rather than relying on g_snprintf().
* | add a courtesy message to let observers know that test-device isn't stuck, ↵Charles Kerr2014-03-191-0/+7
| | | | | | | | it's just slow.
* | when choosing a primary device and more than one battery is found, ↵Charles Kerr2014-03-191-65/+95
|/ | | | accumulate their percentages and time-remaining properties as per the spec revisions in bug #880881.
* update the header / menuitem text / accessible text to reflect the changes ↵Charles Kerr2014-03-042-41/+113
| | | | in https://wiki.ubuntu.com/Power?action=diff&rev2=44&rev1=43#Title
* Adding basic acceptance testsTed Gould2014-01-311-0/+24
|
* use the correct battery icon when charging/dischargingCharles Kerr2013-10-011-12/+12
|
* update the tests to look at the 24 hour thresholdCharles Kerr2013-08-231-3/+3
|
* copyediting: remove trailing spaces in source codeCharles Kerr2013-08-223-25/+25
|
* add show-percentage feature, basing off Haw Loeung's patch.Charles Kerr2013-08-221-33/+79
|
* get test-devices building and passing again.Charles Kerr2013-06-173-59/+63
|
* first steps at fixing the tests that broke during GMenuificationCharles Kerr2013-06-162-9/+6
|
* Make use of XORG_GTEST_LDFLAGS that xorg-gtest can export to know whether ↵Mathieu Trudel-Lapierre2013-03-051-0/+1
| | | | there are extra libraries we should link against.
* Fix path to gtest sources.Mathieu Trudel-Lapierre2013-01-221-2/+2
|
* remove g_type_init() calls and bump glib minimum to 2.35.4, where ↵Charles Kerr2013-01-173-46/+0
| | | | g_type_init() is deprecated
* explicitly cast integral values to the correct type when passing them to a ↵Charles Kerr2012-11-161-4/+4
| | | | varargs function.
* modify DeviceTest.Labels s.t. it fails (currently failing) if the 'short' ↵Charles Kerr2012-11-071-1/+1
| | | | string for an AC Adapter is nonempty.
* in TestDevice.ChoosePrimary, add another test (currently failing) to confirm ↵Charles Kerr2012-11-061-0/+1
| | | | that when indicator-datetime is choosing from devices that are neither charging nor discharging, batteries are more interesting than other devices, and other devices are more interesting than UP_DEVICE_KIND_LINE_POWER
* add unit test (currently failing) to test for the bug reported in LP bug ↵Charles Kerr2012-11-061-11/+15
| | | | #1075192
* in TestDevice, make the log variable names a little more consistentCharles Kerr2012-10-281-14/+14
|
* set DeviceTest's gwarning/gcritical log func to one that prints no messages ↵Charles Kerr2012-10-281-0/+31
| | | | but accumulates the log count. This way we can both (a) silence in-console warnings that look like bugs in the test but are actually desirable warnings generated by fuzz testing, and (b) assert that we get exactly as many warnings/criticals as we expect to get.
* expand DeviceTest.ChoosePrimary to test choosing from a wider variety of ↵Charles Kerr2012-10-281-67/+44
| | | | device states.
* add test (currently failing) to detect the logic error reported in bug #1071757Charles Kerr2012-10-261-0/+16
|
* fix comment typoCharles Kerr2012-10-261-1/+1
|
* Select the primary device based on the spec's criteria. Add tests to confirm.Charles Kerr2012-10-261-0/+75
|
* silence the known/nonbug gtk and glib warningsCharles Kerr2012-10-261-0/+12
|
* add unit tests to confirm the device refcounts are correct s.t. ↵Charles Kerr2012-10-261-0/+2
| | | | IndicatorPower isn't leaking devices
* the device kind string wasn't being used in some icon names.Charles Kerr2012-10-251-145/+196
|
* when discharging the battery, prefer the percent-charged icons over the ↵Charles Kerr2012-10-031-7/+15
| | | | full,good,low icons because the former show a more accurate view of the charge.