[CLOSED] Testing Strategy / Story

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.

TL;DR

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.

Honestly, mocking is the easy way around performing test with the SDK. That being said, what I do is create 2 projects when building an app.

I'm not saying it's optimal, but it's what I started doing and it works lol

I use one project for the actual development, and the other with fake data for testing. It requires a lot of manual work to set up a testing environment, but you should be able to create a function that just clones a project on-demand.