Choosing better points to output "start" events for TAPL
Now doing this before branching points, thus avoiding flakes when the execution can go to an unexpected branch and not produce an event. Bug: 153824894 Change-Id: If117da0498eaf2d94c9610552724981be34c6569
This commit is contained in:
1 parent
047a54a21f
commit
cf275c1bd7
15 files changed
+29
-18
No files matched your search
@@ -94,7 +94,7 @@ public class AddConfigWidgetTest extends AbstractLauncherUiTest {
|
||||
WidgetConfigStartupMonitor monitor = new WidgetConfigStartupMonitor();
|
||||
widgets.
|
||||
getWidget(mWidgetInfo.getLabel(mTargetContext.getPackageManager())).
|
||||
dragToWorkspace(true);
|
||||
dragToWorkspace(true, false);
|
||||
// Widget id for which the config activity was opened
|
||||
mWidgetId = monitor.getWidgetId();
|
||||
|
||||
|
||||
Reference in new issue
Block a user