docs: review regression-testing-extension - #62
Conversation
WalkthroughThis PR updates the Regression Testing extension documentation to reflect product version 5.1.5, restructures navigation paths to route through the Monitoring section, revises General and Automated Scan Settings descriptions, adjusts manual scan instructions, changes scheduled scanning behavior from per-page to batch processing, and updates Related Resources links. ChangesRegression Testing Extension Documentation
Estimated code review effort🎯 2 (Simple) | ⏱️ ~8 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 inconclusive)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@add-ons/security/regression-testing-extension.mdx`:
- Line 101: Change the section heading text "Notifications Settings" to the
singular form "Notification Settings"; locate the markdown/MDX heading token
(the line containing ### **Notifications Settings**) and replace the inner text
so the heading becomes ### **Notification Settings** to match the standard
UI/docs wording.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: f371bd26-31a7-4b25-9060-9cac6ebb01b3
📒 Files selected for processing (1)
add-ons/security/regression-testing-extension.mdx
| • **Automated scans** and **Automated scans frequency** – Choose how often automatic scans run: Once a day, Once a week, Twice a month, Once a month. | ||
|
|
||
| ### **Notification Settings** | ||
| ### **Notifications Settings** |
There was a problem hiding this comment.
Use singular section heading for consistency
Line 101 should be “Notification Settings” (not “Notifications Settings”) to match standard UI/docs wording.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@add-ons/security/regression-testing-extension.mdx` at line 101, Change the
section heading text "Notifications Settings" to the singular form "Notification
Settings"; locate the markdown/MDX heading token (the line containing ###
**Notifications Settings**) and replace the inner text so the heading becomes
### **Notification Settings** to match the standard UI/docs wording.
Summary by CodeRabbit