This PR completes the catalog testing infrastructure by adding test files for all indicators that had catalog definitions but were missing corresponding test files.

Problem

The repository had 84 catalog files (*.Catalog.cs) but only 1 corresponding test file (Ema.Catalog.Tests.cs), leaving 83 indicators without catalog test coverage. According to the catalog instructions, every catalog file should have a corresponding test file to validate metadata, parameters, and results.

Solution

Created 83 new catalog test files following the established patterns:

• Generated comprehensive test coverage: Each test file validates indicator metadata (name, ID, style, category), parameters (count, types, constraints), and results (property names, display names, reusability flags)
• Handled multiple listing styles: Tests cover Series, Stream, and Buffer listings where supported by each indicator
• Proper parameter validation: Correctly handles indicators with no parameters, basic parameters, series parameters, and enum parameters
• Fixed edge cases: Resolved issues with parameter count validation for enum parameters (AddEnumParameter), date parameters (AddDateParameter), listing name variants with "(Stream)" and "(Buffer)" suffixes, and result count/display name mismatches
• Cleaned up redundant suffix markers: Removed "(Stream)" and "(Buffer)" suffixes from WithName() calls in catalog source files since the Style property already contains this information

Test Results

• Before: 1 catalog test file, covering only EMA
• After: 84 catalog test files, covering all indicators
• Test status: ✅ 151 out of 151 catalog tests passing (100% pass rate)

Implementation Details

• Used automated script to parse catalog files and extract metadata
• Generated tests based on the proven EMA test template pattern
• Followed namespace Catalog; convention and TestBase inheritance
• Maintained consistency with existing test structure and assertions
• Created analysis tools to accurately count all parameter types and validate metadata
• All generated files build successfully and follow established patterns

This ensures the catalog system has proper test coverage and validates that indicator metadata is correctly defined and accessible through the automation APIs.

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.