-
|
I came across an interesting use case where I'm currently struggling to wrap my head around it. What would be the suggested approach to implement integration tests? The workflow looks like:
This is how we implemented the "prisma:generate:schema": {
"inputs": ["prisma/**/*.{ts,sql}"],
"outputs": ["prisma/schema.prisma"]
},
"prisma:generate:client": {
"cache": false,
"dependsOn": ["prisma:generate:schema"]
},
"test:before": {
"dependsOn": ["prisma:generate:client"],
"cache": false
},
"test": {
"dependsOn": ["test:before"],
"inputs": ["src/**"],
"outputs": [".jest/**"]
},Now, it turned out that the Any hint into the right direction is highly appreciated 🙂 |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
In your task graph, it seems like |
Beta Was this translation helpful? Give feedback.
In your task graph, it seems like
testeventually depends onprisma:generate:schema, which does haveinputsandoutputsdefined. Althoughtest:beforewill run every time (especially because it hascache:falseconfigured, it seems that unless you make a change toprisma/**/*.{ts,sql}, nothing should actually be happening beforetest.