akanealw/Charon
1
0
Fork 0
Code Issues Pull Requests Actions 16 Packages Projects Releases Wiki Activity

fix(tests): enhance system settings tests with feature flag propagation and retry logic

Browse Source 
- Added initial feature flag state verification before tests to ensure a stable starting point.
- Implemented retry logic with exponential backoff for toggling feature flags, improving resilience against transient failures.
- Introduced `waitForFeatureFlagPropagation` utility to replace hard-coded waits with condition-based verification for feature flag states.
- Added advanced test scenarios for handling concurrent toggle operations and retrying on network failures.
- Updated existing tests to utilize the new retry and propagation utilities for better reliability and maintainability.
This commit is contained in:
GitHub Actions
2026-02-02 01:14:30 +00:00
parent 9f7ed657cd
commit f19632cdf8
14 changed files with 5668 additions and 811 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
.github/instructions/features.instructions.md vendored
View File

@@ -9,8 +9,8 @@ When creating or updating the `docs/features.md` file, please adhere to the foll
## Structure
- This document should provide a short, to the point overview of each feature. It is used for marketing of the project. A quick read of what the feature is and why it matters. It is the "elevator pitch" for each feature.
- Each feature should have its own section with a clear heading.
- This document should provide a short, to the point overview of each feature. It is used for marketing of the project. A quick read of what the feature is and why it matters. It is the "elevator pitch" for each feature.
- Each feature should have its own section with a clear heading.
- Use bullet points or numbered lists to break down complex information.
- Include relevant links to other documentation or resources for further reading.
- Use consistent formatting for headings, subheadings, and text styles throughout the document.
@@ -24,3 +24,7 @@ When creating or updating the `docs/features.md` file, please adhere to the foll
- Ensure accuracy and up-to-date information.
## Review
- Changes to `docs/features.md` should be reviewed by at least one other contributor before merging.
- Review for correctness, clarity, and consistency with the guidelines in this file.
- Confirm that each feature description reflects the current behavior and positioning of the project.
- Ensure the tone remains high-level and marketing‑oriented, avoiding deep technical implementation details.