zec
/
secant-android-wallet
mirror of https://github.com/zcash/secant-android-wallet.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
secant-android-wallet/ui-lib/src/androidTest/AndroidManifest.xml

13 lines
338 B
XML
Raw Normal View History

[#28] Initial SDK integration This sets up the infrastructure needed to continue implementing the onboarding UI for create and import of wallets. By fleshing out the global state management in the app now, we can better manage asynchronous IO to avoid blocking the UI. This adds: - Load and persistence a wallet in encrypted preferences - The stored data is written as a single JSON object, as opposed to multiple entries, to ensure atomic writes - The data is versioned, so that we can change the JSON format readily in the future - Detection of application state, e.g. onboarding versus loading the user's wallet - Touch points to initialize the SDK
2021-11-12 04:09:30 -08:00
<?xml version="1.0" encoding="utf-8"?>
<manifest
[#586] AGP 7.3
2022-09-19 05:24:19 -07:00
xmlns:android="http://schemas.android.com/apk/res/android">
[#28] Initial SDK integration This sets up the infrastructure needed to continue implementing the onboarding UI for create and import of wallets. By fleshing out the global state management in the app now, we can better manage asynchronous IO to avoid blocking the UI. This adds: - Load and persistence a wallet in encrypted preferences - The stored data is written as a single JSON object, as opposed to multiple entries, to ensure atomic writes - The data is versioned, so that we can change the JSON format readily in the future - Detection of application state, e.g. onboarding versus loading the user's wallet - Touch points to initialize the SDK
2021-11-12 04:09:30 -08:00
<application
[#71] Add re-creation test for onboarding - Created dedicated test activity for integration tests. - Created Onboarding integration test class with two state restoration tests. - Moved OnboardingTestSetup to its own class. - Filed related issues.
2022-04-14 09:34:12 -07:00
android:label="zcash-ui-test" >
<activity
[#209] Compose dependency update * [#209] Update Compose dependency to latest version 1.2.0-beta03 - Update dependency - Align our integration tests with the new Compose requirements - Add integration folder to tests, if missing - Split integration tests, which require activity to separate classes - Remove unnecessary custom activity for each integration app part and create one custom common activity - Implement Downloadable fonts from Compose 1.2 - Update Third party licenses documentation
2022-06-13 23:50:55 -07:00
android:name="co.electriccoin.zcash.ui.common.UiTestingActivity"
[#211] check for app updates - Basic screen UI scaffolding. - Set up communication with Google Play in-app update API. - Mocking communication with Google Play API. - Added unit, UI and integration tests for the in-app update screen model, util, view and viewmodel classes. - Added mock implementation of helper AppUpdateChecker class. - Introduced ViewModel integration test. - Filed issue for future manual testing of implemented in-app update mechanisms after the wallet app is released on Google Play. - Implement FakeAppUpdateManager in AppUpdateCheckerMock instead of the ugly AppUpdateInfo instantiation - this affected the tests too. Co-authored-by: Carter Jernigan <git@carterjernigan.com>
2022-05-16 04:40:50 -07:00
android:exported="false" />
[#71] Add re-creation test for onboarding - Created dedicated test activity for integration tests. - Created Onboarding integration test class with two state restoration tests. - Moved OnboardingTestSetup to its own class. - Filed related issues.
2022-04-14 09:34:12 -07:00
</application>
[#28] Initial SDK integration This sets up the infrastructure needed to continue implementing the onboarding UI for create and import of wallets. By fleshing out the global state management in the app now, we can better manage asynchronous IO to avoid blocking the UI. This adds: - Load and persistence a wallet in encrypted preferences - The stored data is written as a single JSON object, as opposed to multiple entries, to ensure atomic writes - The data is versioned, so that we can change the JSON format readily in the future - Detection of application state, e.g. onboarding versus loading the user's wallet - Touch points to initialize the SDK
2021-11-12 04:09:30 -08:00
</manifest>