Write tests for native automation feature

[bartekpacia]

Patrol's native automation feature doesn't have enough tests. We need to change this.

tap

Test cases:

• 1
  • given: a screen with 2 views with "Log in" text
  • when: tap(Selector(text: "Log in")) is called
  • then: the first view is tapped
• 2
  • given: a screen with 2 views with "Log in" text
  • when: tap(Selector(text: "Log in", index: 1)) is called
  • then: the second view is tapped
• 3
  • given: a screen with 2 views with "Log in" text, but the 2nd view appears only after a few seconds
  • when: tap(Selector(text: "Log in", index: 1)) is called
  • then: the second view is tapped once it becomes visible

enterText

Test cases:

• 1
  • given: a screen with 2 text fields with "Username" hints
  • when: enterText(Selector(index: 0), "Jane") is called
  • then: the first view is tapped
• 2
  • given: a screen with 2 text fields with "Username" hints
  • when: enterText(Selector(index: 1), "Jane") is called
  • then: the second view is tapped
• 3
  • given: a screen with 2 text fields with "Username" hints, but the 2nd text field appears only after a few seconds
  • when: enterText(Selector(index: 1), "Jane") is called
  • then: the second view is tapped once it becomes visible

Why is enterTextByIndex() not used above? I suggest removing/deprecating enterTextByIndex(). So instead of:

enterTextByIndex("Jane", 0);
enterTextByIndex("Appleseed", 1);

developers will write:

enterText(Selector(index: 0), "Jane");
enterText(Selector(index: 1), "Appleseed");

[bartekpacia]

More random ideas that we should introduce to Patrol:

• matrix of various Android and iOS versions
• when should we run them? on every push to PR? just before PR merge? nightly?
• setUp, tearDown, setUpAll, tearDownAll
  • in deeply nested groups
  • when tests fail/crash
  • during patrol develop
• test tests that fail/crash
• across all officially supported device farms: FTL, BS, emulator.wtf, GitHub Actions (maybe with its large runners), CirrusCI)
• split "the real example app" (for our users, to demo our features) from example apps that test Patrol itself (like the internal directory) (see #1932)
• test native automation feature ($.native) on new "example test apps" (that we'll have to create) (see #1950)
• improve observability of Patrol's test suite. Visualize trends. Introduce something like Grafana.