h3. 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 {color:#59afe1}team-service-2{color}
h3. Steps
*In Memory*: http://docs.aerogear.org/aerogear/latest/data-sync.html#in-memory-option
* Create a in memory data source (Name must not be allowed to be blank) (/)
* A warning is displayed when this type is selected (/)
*Postgres*: http://docs.aerogear.org/aerogear/latest/data-sync.html#postgres-option
* Create a postgres data source (Name must no be allowed to be blank) (Memeolist one can be found at https://github.com/aerogear/data-sync-server/blob/master/sequelize/seeders/memeolist-example-postgres.js#L7 ) (/)
* Verify all validation works (/)
* Verify the Test feature returns success for a valid Postgres connection (/)
* Verify the Test feature returns failure for an invalid Postgres connection (/)
*General Datasource*
* Ensure a data source can be edited: http://docs.aerogear.org/aerogear/latest/data-sync.html#edit-an-existing-data-source (/)
* Ensure a datasource can be deleted: http://docs.aerogear.org/aerogear/latest/data-sync.html#delete-an-existing-data-source (/)
* Ensure that when a data source is deleted and it had no resolvers are attached - that it displays a message showing this (/)
* Ensure that when a data source is deleted and it has attached resolvers - that it displays a message warning that they will be deleted also (verify that they have then been deleted) (!)
* Check that the filtering feature works for the data sources - if no match it should display info on the page to say this (/)
|
|
