frameworks_base

Android/frameworks_base

Fork 0

Commit Graph

Author	SHA1	Message	Date
Roshan Pius	f145e1732e	TestLooper: Some changes to test looper behavior a) Add a new stopAutoDispatchAndIgnoreExceptions method This method ignores exceptions raised when there are no messages dispatched in the looper. Helps write negative unit tests for methods where the runnables are not posted when some preconditions are not met. Not starting the looper in these tests would make it unclear whether the test failed because the looper was not running or because the preconditions (like permission checks) where not satisfied. b) Auto dispatch will only stop running when stopAutoDispatch is invoked. Previously it stops running when it runs a single message. This causes failures in unit tests for methods which posts multiple runnables in the same method. Bug: 138403307 Bug: 117601161 Test: atest com.android.server.wifi Change-Id: Iab27d92d443c6d7364c52b86d51dd2cb7902358a	2019-09-19 20:41:32 -07:00
Etan Cohen	cff2fe4f76	Add Executor to the TestLooper Add a method to obtain an Executor from a TestLooper: the executor executes on a new Handler on the test looper. Bug: 73088768 Test: new unit test for executor Change-Id: Ib0aa10011116a4d998f8d3a7434939338d9b516d	2018-02-16 10:13:26 -08:00
Christopher Wiley	07630f6bd3	Create frameworks-base-testutils lib This permits sharing of test components used in connectivity tests. Rename the MockLooper to TestLooper, reflecting that it is not a true mock, but a manually controlled Looper for use in tests. Bug: 28848133 Test: Tests consuming this library pass. Change-Id: I57e11f9544c7bffdb02739ab2a921512b1b11874	2016-05-19 13:12:09 -07:00

Author

SHA1

Message

Date

Roshan Pius

f145e1732e

TestLooper: Some changes to test looper behavior

a) Add a new stopAutoDispatchAndIgnoreExceptions method
This method ignores exceptions raised when there are no messages
dispatched in the looper. Helps write negative unit tests for methods where
the runnables are not posted when some preconditions are not met.
Not starting the looper in these tests would make it
unclear whether the test failed because the looper was not running or
because the preconditions (like permission checks) where not satisfied.
b) Auto dispatch will only stop running when stopAutoDispatch is
invoked. Previously it stops running when it runs a single message. This
causes failures in unit tests for methods which posts multiple runnables
in the same method.

Bug: 138403307
Bug: 117601161
Test: atest com.android.server.wifi
Change-Id: Iab27d92d443c6d7364c52b86d51dd2cb7902358a

2019-09-19 20:41:32 -07:00

Etan Cohen

cff2fe4f76

Add Executor to the TestLooper

Add a method to obtain an Executor from a TestLooper: the executor
executes on a new Handler on the test looper.

Bug: 73088768
Test: new unit test for executor
Change-Id: Ib0aa10011116a4d998f8d3a7434939338d9b516d

2018-02-16 10:13:26 -08:00

Christopher Wiley

07630f6bd3

Create frameworks-base-testutils lib

This permits sharing of test components used in connectivity tests.
Rename the MockLooper to TestLooper, reflecting that it is not a
true mock, but a manually controlled Looper for use in tests.

Bug: 28848133
Test: Tests consuming this library pass.

Change-Id: I57e11f9544c7bffdb02739ab2a921512b1b11874

2016-05-19 13:12:09 -07:00

3 Commits