[MAINTENANCE] Streamline user scenario testing workflow and VS debugging config

[yunlishao]

Task Summary
Implement two workflow improvements for handling user scenarios:

1. Establish a streamlined process to integrate user-uploaded scenarios (from OneDrive file request) into a centralized FIXS branch for debugging, while maintaining privacy between different users' scenarios
2. Improve Visual Studio debugging workflow to eliminate manual debuggerCommandArguments changes when testing different config.yaml files

Why is this needed?
Currently:

• Users upload proprietary scenario files via OneDrive file request portal, but there's no standardized git workflow for integrating these into FIXS for debugging
• Need to maintain privacy - users should not see other users' proprietary scenarios
• When debugging in Visual Studio, developers must manually update debuggerCommandArguments in project settings each time they switch scenarios, which is tedious and error-prone

Scope of Work
Task 1: User scenario integration workflow

• Design a git branching strategy that allows private debugging of user scenarios
• Integrate with existing OneDrive file request portal: https://outlookuga-my.sharepoint.com/:f:/g/personal/ys04893_uga_edu/EmyW7v04lJhGh263oGvKDfwBMunLjrKmkOkgKDoGfshXVQ
• Explore solutions that maintain privacy between users while allowing maintainers to debug
• Document the workflow for receiving scenarios → creating branch → testing → resolving issues

Considerations to explore:

• Branch-per-user vs. branch-per-issue strategies
• Integration with issue tracking (e.g., issue #X corresponds to branch/directory)
• .gitignore patterns for proprietary files if needed
• Cleanup/archival process after issues are resolved

Task 2: Visual Studio debugging configuration

• Explore alternatives to manual debuggerCommandArguments editing
• Current pain point: Must manually change debugger arguments in VS project settings when switching between different config.yaml files
• Potential solutions to investigate:
  • Hardcoded debug config path (e.g., always read from tests/DebugScenario/config.yaml in VS debug mode)
  • VS launch profiles with pre-configured argument sets
  • Environment variable-based config path resolution
  • CMake/MSBuild property sheets for debug configurations

Components affected:

• Git repository structure and branching strategy
• TrafficLayer/TrafficLayer/mainTrafficLayer.cpp - Config file loading logic
• Visual Studio project files (.vcxproj, .vcxproj.user)
• CommonLib/ConfigHelper.h/cpp - May need updates depending on solution
• Documentation for maintainers on user scenario workflow

Environment (if version-specific)

• C++ compiler/version: Visual Studio 2022
• Git workflow/repository management

Risks or Dependencies

• Solution for Task 1 must not expose proprietary user data to other users
• Solution for Task 2 should not break existing build/test workflows

Additional Context (optional)
This is an exploratory maintenance task - solutions will be designed during implementation.

Related context:

• Bug report template already references OneDrive upload link for scenario submission

Open questions to resolve during implementation:

• How to structure git branches for private user scenarios?
• Best approach for VS debugging without manual config changes?
• Can we leverage VS 2022 features like launch.vs.json or similar?

[yunlishao]

Task 1: User Scenario Integration Workflow ✅

Created tests/UserScenarios/ directory with workflow for handling user-provided proprietary scenarios.

Key features:

• Folder structure tracked via .gitkeep (exists in all branches)
• All scenario contents gitignored (maintains privacy between users)
• Full IDE/debugging access without committing proprietary files
• Issue-linked subdirectory approach: tests/UserScenarios/issue_X_description/

See tests/UserScenarios/README.md for complete workflow documentation.

Next: Task 2 - Visual Studio debugging configuration improvements

[yunlishao]

Implementation Complete ✅

Both tasks have been implemented and are ready for review in PR (to be created).

Task 1: User Scenario Integration Workflow

Commit: 2c73625

Created tests/UserScenarios/ directory with complete workflow:

• Folder structure tracked via .gitkeep (exists in all branches/worktrees)
• All scenario contents gitignored (maintains privacy)
• Issue-linked subdirectory approach: tests/UserScenarios/issue_X_description/
• Full documentation in tests/UserScenarios/README.md

Task 2: Visual Studio Debugging Configuration

Commit: 533779f

Implemented automatic config discovery:

• Single scenario: Just hit F5 - auto-discovers YAML in tests/UserScenarios/
• Multiple scenarios: Create TrafficLayer/.active_config to select which one
• Other test scenarios: Point .active_config to any config path
• Deployment: Requires explicit -f flag

Technical details:

• Cross-platform (WIN32 + POSIX implementations)
• C++11 compatible
• No manual VS project settings changes needed
• Per-worktree .active_config file (gitignored)

Files changed:

• TrafficLayer/TrafficLayer/mainTrafficLayer.cpp - Auto-discovery logic
• TrafficLayer/TrafficLayer/TrafficLayer.vcxproj.user - Removed hardcoded args
• .gitignore - Added patterns for UserScenarios and .active_config
• tests/UserScenarios/README.md - Complete workflow documentation

Ready for PR and testing.