Hello, @ajitgoel, welcome to the Redwood Community forum
Your problem might be the same that took me a long time to solve (meaning that I am a RedwoodJS novice a bit longer than you are). However, my case has nothing to do with testing (did not reach that point yet) - it the issue with hydrating the database cloned from GitHub
When you create a clone of an RW application (RW is RedwoodJS alias), the state of this application is different from this identical application that you typed in from scratch - Quick Start is a good example of such mini-tutorial.
The difference between the clone and the original stems from the .gitignore file, which is used to filter out parts of your original app when you “push” it to GitHub:
Your application’s database is not persisted in Github - and such behavior gave me a lot of a hard time because I could not find any document that explains how to solve this. By using the trial and error method, I deduced that cloning a RedwoodJS app GitHub
requires one additional step after git clone ...
yarn rw prisma migrate dev
This will bring the clone to the point where the dev.db exists:
but is empty
Open question:
- Is this behavior that I just described a feature or a bug (I could envision that the command
yarn rw dev could include the command yarn rw prisma migrate dev, just like the command yarn create redwood-app my-redwood-app invokes yarn install behind the scene). I do not have sufficient RW experience to claim that it is a bug, but would dare to say that the fix for your problem yarn rw prisma migrate dev should be a part of the documentation for beginners.
