Description
- This is a task for verification of documentation and functionality of Data Sync service
- If you find any flaw or inconsistency in documentation, update this JIRA with its description: AEROGEAR-7894 - general verification of documentation was already done, so we'll try to fix all the mistakes found in the scope of one JIRA
- If you find any bug, file a new JIRA and add it to the backlog with label team-service-2
Steps This test should go through the whole process from provisioning data sync service to testing on Android device. Usually we use Memeolist example to test all around data sync. With this E2E test we should not use Memeolist, but create everything from scratch. One of the reasons why to not use Memeolist example is that with memeolist preparation scrpits we directly populate our postgre db (not data source, but the one used by data-sync-server/ui) with records, which should otherwise be created by data-sync-ui while user interacts with it.
- Provision Data Sync service: http://docs.aerogear.org/aerogear/latest/data-sync.html#provisioning-data-sync-service
- Register Android mobile client: http://docs.aerogear.org/aerogear/latest/getting-started.html#registering
- Bind data sync with mobile client: http://docs.aerogear.org/aerogear/latest/data-sync.html#binding-a-mobile-client-with-the-data-sync-service
- Create new in-memory data source: http://docs.aerogear.org/aerogear/latest/data-sync.html#ui
- Define a schema: http://docs.aerogear.org/aerogear/latest/data-sync.html#schema
- Add resolvers: http://docs.aerogear.org/aerogear/latest/data-sync.html#resolvers
- Create new Android app and follow http://docs.aerogear.org/aerogear/latest/data-sync.html#sdk to test queries and mutations (just log the responses to console and verify that they are correct)
- Verify that subscriptions work correctly
|