Add Developer Error Simulation API (Random, Custom, Delay, Chaos)#26
Open
tabrez-rabbani wants to merge 3 commits intoankurdotio:mainfrom
Open
Add Developer Error Simulation API (Random, Custom, Delay, Chaos)#26tabrez-rabbani wants to merge 3 commits intoankurdotio:mainfrom
tabrez-rabbani wants to merge 3 commits intoankurdotio:mainfrom
Conversation
Author
|
@ankurdotio This is part of my Cohort 2.0 learning contribution. Would love your feedback! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR introduces a Developer Error Simulation API to help frontend and mobile developers test real-world failure scenarios such as authentication errors, database failures, latency issues, and chaos engineering patterns.
Features added:
This module is educational and useful for testing UI error handling and retry mechanisms.
This contribution is part of my learning journey in Cohort 2.0, where I am currently studying full-stack development.