Timeline for API tests against production DB with no endpoints to set up test data
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 16, 2020 at 19:31 | answer | added | PDHide | timeline score: 2 | |
| Jan 16, 2020 at 17:15 | comment | added | pavelsaman | I'll read that. We use MS technologies like Azure and C#, so I'd need to read up on that. | |
| Jan 16, 2020 at 17:03 | comment | added | João Farias | Ok, so the problem is not on the application, but on the infrastructure. Most build systems provide its own checking libraries, which you can use to validate them: github.com/jenkinsci/JenkinsPipelineUnit. Tell if this makes sense in your case, so I will transform in an answer. | |
| Jan 16, 2020 at 16:57 | comment | added | pavelsaman | @João Farias: wrong deployment, different deployment - devs deploying different commits to staging than was on dev, which happens every now and then. | |
| Jan 16, 2020 at 16:42 | comment | added | João Farias | What risks have you identified can only be investigated on a different env than dev? | |
| Jan 16, 2020 at 15:49 | history | asked | pavelsaman | CC BY-SA 4.0 |