Fix "test" db provisioning #3914
Conversation
![gitstart-app[bot]](https://avatars.githubusercontent.com/in/46283?s=60&v=4){kind=small}
Co-authored-by: v1b3m <vibenjamin6@gmail.com>
gitstart-twenty
changed the title
|
Hello @charlesBochet, I initially focused on getting the tests to run smoothly. Unfortunately, the generated GraphQL schemas had duplicate types, leading to test failures. Disabling automatic schema generation and manually providing a schema resolved the issue. However, I foresee potential drawbacks with this approach, particularly the need to update the schema file whenever there are changes to the schema. What are your thoughts at first glance? |
|
@charlesBochet I've merged with main and recent changes, we should be able to find a way to generate a test schema as we do with pre-sign-in on the frontend ? |
|
Yes, we should tackle this one this week, I think we have all the pieces now |
Alright, Looking forward to it! |
|
Closing this for now since this one is very old and has not been updated for a while, let's reopen when we get back to it! (cc @charlesBochet) |
Description
We used to have a "test" database and some script to provision it. It's not working anymore since 0.2 though.
Refs
#3862
Demo
Fixes #3862