| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
This suppression only affects the Android app.
The CVE will instead be tracked externally and will likely be mitigated
by either updating affected dependencies or by identifying that it
doesn't affect the app.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Adds a mechanism to remove all keys/devices of a specified account in
order to start all tests with a known state. This is achieved using a
simple http client included in the e2e test apk, which support login,
listing devices and removing devices.
Two account used for testing _must_ be specified either as gradle
properties or as runtime arguments to the test runner:
* Local properties (local.properties):
valid_test_account_token=XXXX
invalid_test_account_token=XXXX
* Gradle/CLI arguments:
./gradlew :e2e:assembleDebug -Pvalid_test_account_token=XXXX -Pinvalid_test_account_token=XXXX
* Runtime arguments:
am instrument -e valid_test_account_token XXXX -e invalid_test_account_token XXXX # ...
|
|
|
|
This rule will capture screenshot of any failed test and download it to
the host executing the test.
|
|
Most/all tests will inherit from this common base class that will hold
necessary setup steps to run various e2e test scenarios.
|
|
The purpose of this test module is to be able to trigger end-to-end
tests separately from the main app module, mainly because of the flaky
nature of end-to-end tests.
Tests are easiest executed by running the following gradle command:
./gradlew :e2e:connectedDebugAndroidTest
|
