tbsvttrOriginal post
Rank 1: Thread
What is the general idea of a testing strategy or story both for Appwrite Web apps and server functions? Only really found one Article that suggested mocking Appwrite.
Summary
The user suggests using mocking for testing Appwrite, but finds it to create overhead. They propose using two projects - one for development and the other with fake data for testing. They acknowledge that it requires manual setup but suggest creating a function to clone the project when needed. The user asks for suggestions on a testing strategy or story for Appwrite and mentions finding only one article that suggests mocking Appwrite.
Solution: There is no clear solution provided in the thread.