Timeline for API tests against production DB with no endpoints to set up test data
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 17, 2020 at 8:34 | comment | added | PDHide | @puzzle if they are not ready to have a new DB then use the data which already there without modifying . Remove tests that requires modifying of data , from stagging . Communicate it properly to stake holders | |
| Jan 17, 2020 at 8:29 | comment | added | pavelsaman | I was surprised about this setup as well. However, just like many other things, this is a question of money, which is usually a tricky one in a small company. Anyway, this is a different question, thanks agains for your answer, it helped me think about the problem from a different perspective. | |
| Jan 17, 2020 at 6:58 | comment | added | PDHide | @puzzle you need a new staging database then | |
| Jan 16, 2020 at 21:20 | comment | added | pavelsaman | Thank you. I like the idea with new endpoints. In the other hand, they would be used only for testing purposes, no other app needs them. And about the sync, it is not a sync in fact, there is only two databases, one on the dev env and the other one is the production DB which is also used by the staging env. | |
| Jan 16, 2020 at 19:31 | history | answered | PDHide | CC BY-SA 4.0 |