Avoid test failures when screenshot upload fails due to rate limiting

[ankur22]

What?

When a screenshot is upload to a remote location, when it fails, the whole of the test iteration fails. This is confusing behaviour and in most cases the end user may not be able to action on the failure to prevent it from happening (other than disabling screenshots).

Why?

Screenshots on a whole can be looked upon as a source of information to debug an issue or an extra human step to verify that the site is being displayed correctly. If it fails to upload to the remote server due to a rate limit, it shouldn't stop the core test to fail. This is likely lead users to a false positive and less trust in the test and therefore the product.

How?

Logs is a good example. When a log fails due to rate limiting when uploading to a remote location, the logs are ignored but an error log is printed instead. The test itself continues as always. We want to mimic this behaviour for screenshots in the same rate limited case.

Tasks

Tasks

Beta Give feedback

1. PR
2. Update the k6 release notes

Related PR(s)/Issue(s)

No response