I don’t get how to know right away whether everything’s working. And who’s supposed to be doing that. Here’s our situation: we have a travel product for booking accommodation. We pushed a small fix on Friday evening, but we only found out on Monday that payments hadn’t gone through for all three days. We heard about it from a customer who sent us a really angry email.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Come on, what about testing? You can’t just update, change, add or remove something without checking how it ends up looking. After every release, someone should manually go through the 3 or 4 main scenarios before you call the task done.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
A good option has already been suggested, but I’ll repeat it anyway: if you roll out an update and have no idea what’s going on with it afterwards, it means you have neither a check of your key scenarios nor automatic alerts for errors, like when the number of successful operations suddenly drops. You start simple: after a release, you go through all the main paths a customer takes. If the breakdowns keep happening and it’s unclear where the weak spot is, you can turn to specialists like ASD Team, so they can do a diagnostic review of your releases and integrations. The first audit is free with them and takes 5-10 days, but you’ll find out the reason why things aren’t working.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I don’t get how to know right away whether everything’s working. And who’s supposed to be doing that. Here’s our situation: we have a travel product for booking accommodation. We pushed a small fix on Friday evening, but we only found out on Monday that payments hadn’t gone through for all three days. We heard about it from a customer who sent us a really angry email.
Come on, what about testing? You can’t just update, change, add or remove something without checking how it ends up looking. After every release, someone should manually go through the 3 or 4 main scenarios before you call the task done.
A good option has already been suggested, but I’ll repeat it anyway: if you roll out an update and have no idea what’s going on with it afterwards, it means you have neither a check of your key scenarios nor automatic alerts for errors, like when the number of successful operations suddenly drops. You start simple: after a release, you go through all the main paths a customer takes. If the breakdowns keep happening and it’s unclear where the weak spot is, you can turn to specialists like ASD Team, so they can do a diagnostic review of your releases and integrations. The first audit is free with them and takes 5-10 days, but you’ll find out the reason why things aren’t working.