For quality improvements, and to avoid regressions, the client should
have automatized tests to validate transitions, contents and scenarios.
This patch introduces two examples of tests working with Espresso, which
is integrated with Android Studio.

Some notes:
+ "pm clear" is not executed between all tests, so all the tests should
be considered as one test-suite. If we want to make all the tests
completely independant, the TestOrchester should execute a "pm clear"
between two test. Also because of this, Test are ordered via
Testxxxx.
+ To generate tests the easy way can be:
    + Disable animations on the host device
    + In Android studio, Run, Record Espresso Test
+ Sometimes, elements take time to be shown. In this case, the test
must be completed with waiting events. waitUntilViewIsDisplayed()
can be used for this.

Change-Id: Ie44b2568fb9c8570978d1d1af94562bccba6b6b2

Maxime Callet authored 3 years ago and Adrien Béraud committed 3 years ago

Change-Id: Ieb4a742aa9c49bdbbe7e2ebafa55b0f7958cd913

Change-Id: I9bac6673b4c841785cc0ac53b6e7978142b8f578

Change-Id: I5daa01df2121d30dd3e363a89119b659375047f4

Change-Id: I3ad0e1c1587ae8f5c973c6f5c3279c3a05059fe4

Change-Id: Ie3853dacaf317b6471fe6390613ce9460741f3cc

Maxime Callet authored 3 years ago and Adrien Béraud committed 3 years ago

Change-Id: I5ebddae61ba6ba1a4ad23c797189f0d4f8091266

Change-Id: I0ae31705d9cea205a3263895c654504c0845730d