Extent variables with failed step id/name, and failure message/error
We are using Bugbug’s webhook alerting mechanism to notify the team about test failures. We deduplicate the alerts - so if there’s one fail, next test failures until the issue is resolved do not create new tickets in our system.
The problem is - sometimes the investigation takes a while, and there might be a different issue in the meantime (sometimes much more severe). We’d like to create an alert, if the new fail is of a different ‘kind’ than the fail we currently have in the system.
To differentiate between failures we would need to extend the webhook payload for alerts with failed step id or name, and failure message.
Log in to comment and vote
Comments5
May 26
PinnedShipped!
https://docs.bugbug.io/collaboration/alerts/sending-webhook#:~:text=%7D%2C-,%22failedStep%22,-%3A%20%7B
failedStep is null when there is no failed step :)
Paweł Bylina
May 4
@Filip Szwedo Sorry for my late reply. I’ve missed this feature request.
Would a combination of failed stepId and errorCode be enough?
For example:
stepId: a048f587-1c33-4bd1-88b3-ec9157014e48
errorCode: ELEMENT_DOES_NOT_EXIST
Filip Szwedo
May 4
yes, that would be ideal!
it’s a nice-to-have though, nothing super important
Paweł Bylina
May 14
This is the new structure and we will add those two fields to it
https://docs.bugbug.io/collaboration/alerts/sending-webhook
Paweł Bylina
May 26
@Filip Szwedo shipped!
https://docs.bugbug.io/collaboration/alerts/sending-webhook#:~:text=%7D%2C-,%22failedStep%22,-%3A%20%7B