JEF - Compliance Search Test - Test

Edit

Test Results

Running test...

#68 Failed 429

2025-12-06 11:10:45 (8.09s)

AI: The test failed to retrieve the expected compliance data for LM358, instead encountering a 'Spike arrest violation' error due to rate limiting, returning an HTTP 429 status code instead of the expected 200.

#48 Failed 429

2025-12-06 11:10:44 (7.97s)

AI: The test failed because the API returned an HTTP 429 'Rate Limit Exceeded' error, preventing the retrieval of the expected compliance data.

#27 Failed 429

2025-12-06 11:10:15 (8.12s)

AI: The test case 'JEF - Compliance Search Test - Test' failed because the API returned a 'Rate limit exceeded' error (HTTP 429) instead of the expected compliance search results.

#3 Passed 200

2025-12-05 11:34:46 (11.53s)

AI: The test case 'JEF - Compliance Search Test - Test' passed successfully as the actual response precisely matched the expected response in all aspects.

#2 Passed 200

2025-12-05 08:01:16 (8.33s)

AI: The test passed successfully as the actual response perfectly matched the expected response, indicating no discrepancies in the compliance search results for the specified MPN.

#1 Passed 200

2025-12-05 07:54:48 (4.33s)

AI: The actual response perfectly matched the expected response, indicating a successful test outcome.