[SLING-10860] ServerErrorRetryStrategy should not retry if the code is expected

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: Apache Sling Testing Clients 2.0.10
• Fix Version/s: Apache Sling Testing Clients 3.0.6
• Component/s: Apache Sling Testing Clients
• Assignee: Unassigned
• Reporter: Thierry Ygé
• Created: 08/Oct/21 08:19
• Updated: 12/Sep/22 13:49
• Resolved: 22/Dec/21 15:11

Description

Currently the ServerErrorRetryStrategy would retry for the list of error codes or if not defined default for 500 and above.

Let say you have a a test that expect a 500 or any other code define in the list of error codes.

client.doGet("someurl", 500);

That will then retry a number of time, while in fact this code is expected to happen, so in that case it should not retry.

Since we have control on the "http" context parameter, the expected status codes could be passed in that object , and so used to decide or not if we need a retry too.