Automation lab Aú API Interaction & Mocking (API_INTERACTION)
Lab 038: Handle API rate limit 429
Practice handle api rate limit 429 in a real web app context as part of the API Interaction & Mocking module.
intermediate
intermediate
Objectives
Use for test scripts- Understand the purpose and business flow of handle api rate limit 429.
- Design stable locators for key UI elements.
- Automate user interactions and verify the resulting UI state.
Sandbox
API & Network • api • intermediate • active
Handle API rate limit 429
Track request counts and show 429 when limit exceeded.
Reading and understanding requirements
Choosing stable locators
Designing assertions based on business rules
Learning objectives
- Enforce request window (3 requests max).
- Surface 429 error with retry-after hint.
- Reset window to recover.
Steps
- Send multiple requests quickly.
- See 429 after threshold.
- Reset window and verify success again.
Practice sandbox
Limit: 3 requests per window.
Requests this window: 0
429 Too Many Requests. Retry after 5s.
Request succeeded.
Idle
Assertions to practice
- 429 appears after 3rd request in window.
- Reset clears count and error.
- Status reflects success/error.