Problem Description
I’ve discovered a significant development workflow issue with SubScenarios. When any scenario input is marked as Required = Yes, it becomes impossible to test individual modules within that SubScenario. The error message appears:
Cannot initialize the scenario because of the reason ‘Scenario input validation failed’
Validation failed for 5 parameter(s). Scenario initialization failed with an error.
Current Workaround
The only workaround is to:
- Set all Required fields to
No - Test the individual module
- Remember to set Required fields back to
Yesbefore deployment
This is time-consuming and error-prone.
Inconsistency with Regular Scenarios
In regular scenarios, when testing an individual module that requires inputs, Make prompts for temporary values. This allows isolated testing without modifying the scenario configuration. SubScenarios should behave the same way.
Feature Request
Please implement the same behavior for SubScenarios:
- When executing a single module within a SubScenario
- If that module requires scenario inputs, prompt for temporary values
- Execute the module without requiring full scenario initialization
Business Impact
- Development Efficiency: Constantly toggling Required settings wastes developer time
- Risk of Errors: Developers might forget to re-enable Required settings before deployment
- Testing Complexity: Makes unit testing unnecessarily complicated
Technical Perspective
The purpose of individual module execution is to unit test specific modules in isolation. Scenario-level validation should not apply when we’re not executing the complete SubScenario workflow.
Has anyone else experienced this issue? Please vote if you’d like to see this improvement implemented.
