If you want to be thorough about it, I recently posted a checklist of things one can use to test a relatively unknown service (at least as far as feedback around here goes). This should go over most of the things that can theoretically cause issues with a service. I would say that if it can handle Obsidian’s constant and frequent auto-saving, it will handle Scrivener’s slightly more conservative auto-saving as well, but you’ll find that in the list of checks too.