Currently, when a user is editing a fragment, all progress will be lost If session times out, or if window is closed.
The goal of this story is to implement auto-save in fragment editor, so the progress is saved automatically some seconds after the user edits something.
This way, all these changes will be saved as a draft, and won't be public until user clicks on 'Publish' button.
As a consequence of the implementation of auto-save, we are removing the 'Save as draft' button, as it won't make sense.
When the user is editing a fragment within the fragment editor
Then the changes are saved automatically after some seconds of no activity
|Test Scenarios||Test Strategy||Kind of test||Is it covered by FrontEnd ? (JS-Unit)||Is it covered by BackEnd ? (unit or integration)||Could it be covered by POSHI?|
|The changes are saved automatically in fragment editor before publish||Critical||Manual||No||No||Yes|
|The latest changes are saved automatically in fragment editor when the fragment has a published version||High||Manual||No||No||Yes|
|The imported fragment should have Draft label when it has invalid values||Medium||Manual||No||An integration test can be created||Yes|
|The changes are saved automatically in fragment editor before publish in Staging site||Medium||Manual||No||No||Yes|