Commit Graph
14 Commits
Author SHA1 Message Date
vadimt 6b534ee54f Diagnose when lab device sends fake touch screen events to test
Bug: 189874683
Test: local
Change-Id: I8ac569ab049bafaa0a6263598f2b43a99386e6d9
2021-08-06 15:49:02 -07:00
vadimt cf1c28ef73 Dump accessibility hierarchy on test failure
This will allow seeing exactly what the test sees.

Test: local runs
Bug: 187761685
Change-Id: Ibf4b97bd9b99d4b40def4eb3db9a2cd1b47defb1
2021-07-22 16:00:53 -07:00
Sunny Goyal 420ba54dee Improving hierarchy dump for test failure
Bug: 192003777
Test: Manual
Change-Id: I3223a14cd88beddd76ecae0ae37c6fdce0752bef
2021-06-25 12:41:51 -07:00
vadimt 143748fbf4 Detect leaks only on test success
Bug: 191690396
Test: presubmit

Change-Id: Ie59c3b944d420ac25ebba86bf500fcf33700ca99
2021-06-22 18:49:34 -07:00
vadimt 68e8578588 Not trying to disable running tests after a failed finalizer
Turns out there is no good way to know that an exception comes from a
finalizer.

Change-Id: I0cb2c518d0b7dc20ad7734ed46ba6af1b8a9d36e
2020-02-11 13:27:17 -08:00
vadimt 6c95453a19 Restoring generating screenshots of failures
Now correctly inheriting from a statement.

Change-Id: I7fdf03c8ce144ba31d978950af7e71a09004ae1e
2020-02-07 19:43:08 -08:00
vadimt 8211b6a021 More diags for logic disabling other tests after a finalizer failure
Change-Id: I4af56b2b83b204b9a5a383a26a3d845a88a96bf1
2020-02-04 03:11:06 +00:00
vadimt 053cb7a6e6 Not crashing tests when a test fails to deinitialize
This causes nondescript diags "Test failed to run to completion.
Reason: 'Instrumentation run failed due to 'Process crashed.''. Check
device logcat for details"

Now quietly skipping all consequent tests after such failure.

Change-Id: I3747cda1a3094bfe82e27eae39ba9e9dfd4af9b6
2020-01-27 19:26:00 -08:00
vadimt 2c6316be46 Adding auto-investigation of one more flake
Reshuffling the tests to make the investigator the outmost rule and run
the code that throws the original exception inside the investigator.

Change-Id: I714717a9b616862db5ce59116138ba7ea6ceb971
2020-01-21 19:06:59 -08:00
vadimt cffe99f0bb Automatically diagnosing known flakes
It often takes a long time to fix a flake; meanwhile it takes a lot of
time for sheriffs to identify whether to register a new flake for a
failure.

This CL adds automatic identifies identification of one know flake type.
Once identified, it rewrites the error so that:
1. Flakes clustering tool that has only rudimentary clustering, places
all flakes of this kind in the same cluster (not multiple ones like
now). This is a step towards using clustering tool for monitoring
flakes;
2. Sheriff immediately sees that the issue is known.

Change-Id: I86a0762665cb21434289e1be00b60bd76fec4142
2020-01-21 13:29:37 -08:00
vadimt f13eaa0242 Saving screenshots for failures in NavigationModeSwitchRule
Change-Id: I732076a5eb14b181f560024e2780e2012a81fd95
2019-08-23 14:18:32 -07:00
vadimt cc5b17b351 Improving screenshot path
Change-Id: If61bbf0bbc8ace31142bc0e2d598d72ce48de360
2019-08-13 17:49:15 -07:00
vadimt 26cfff41ba Taking screenshots for local tests for FallbackRecentsTest
Change-Id: I604e7e90f2146069827b520d44db1854edc7aa77
2019-06-25 16:26:33 -07:00
vadimt 7a38854284 Taking local screenshot before navigation state is restored
Change-Id: Id8003b17c68af5b4882bdbf5e14a142875791cbc
2019-06-05 16:18:55 -07:00