Guidelines for testing and validating newly created modes to ensure they function correctly and integrate well with the Roo Code ecosystem.
-
Mode slug is unique and follows naming conventions
No spaces, lowercase, hyphens only
-
All required fields are present and non-empty
slug, name, roleDefinition, groups
-
No customInstructions field in .roomodes
All instructions must be in XML files in .roo/rules-[slug]/
-
File restrictions use valid regex patterns
.
your_file_regex_here
]]>
-
whenToUse clearly differentiates from other modes
Compare with existing mode descriptions
-
XML files are well-formed and valid
No syntax errors, proper closing tags
-
Instructions follow XML best practices
Semantic tag names, proper nesting
-
Examples use correct tool syntax
Tool parameters match current API
-
File paths in examples are consistent
Use project-relative paths
-
Mode appears in mode list
Switch to the new mode and verify it loads
-
Tool permissions work as expected
Try using each tool group and verify access
-
File restrictions are enforced
Attempt to edit allowed and restricted files
-
Mode handles edge cases gracefully
Test with minimal input, errors, edge cases
Configuration Testing
Verify mode appears in available modes list
Check that mode metadata displays correctly
Confirm mode can be activated
I've created the mode configuration. Can you see the new mode in your mode list?
Yes, I can see the new mode and switch to it
No, the mode doesn't appear in the list
The mode appears but has errors when switching
]]>
Permission Testing
Use read tools on various files
All read operations should work
Try editing allowed file types
Edits succeed for matching patterns
Try editing restricted file types
FileRestrictionError for non-matching files
Workflow Testing
Execute main workflow from start to finish
Test each decision point
Verify error handling
Check completion criteria
Integration Testing
Orchestrator mode compatibility
Mode switching functionality
Tool handoff between modes
Consistent behavior with other modes
Mode doesn't appear in list
Syntax error in YAML
Invalid mode slug
File not saved
Check YAML syntax, validate slug format
File restriction not working
Invalid regex pattern
Escaping issues in regex
Wrong file path format
Test regex pattern, use proper escaping
Mode not following instructions
Instructions not in .roo/rules-[slug]/ folder
XML parsing errors
Conflicting instructions
Verify file locations and XML validity
Verify instruction files exist in correct location
.roo
true
]]>
Check mode configuration syntax
.roomodes
]]>
Test file restriction patterns
.
your_file_pattern_here
]]>
Test incrementally as you build the mode
Start with minimal configuration and add complexity
Document any special requirements or dependencies
Consider edge cases and error scenarios
Get feedback from potential users of the mode