- Update line counts across documentation to match actual source files
(test-config-parser.c: 3304 lines, test-stubs.c: 219 lines)
- Correct test configuration count to exact "25 configs"
- Fix schema file references to single canonical file
- Add property database documentation with accurate statistics
- Fix broken Makefile regeneration targets (regenerate-property-db,
regenerate-platform-property-db) to use correct schema-based workflow
- Replace non-existent rebuild-property-database.py with three-step
process: extract-schema-properties.py → generate-database-from-schema.py
Signed-off-by: Mike Hansen <mike.hansen@netexperience.com>
Fix platform property tracking in test output
Platform databases now always included for property analysis, showing
complete base→platform flow with arrow notation in test reports.
Signed-off-by: Mike Hansen <mike.hansen@netexperience.com>
Enables undefined property detection during make validate-schema, providing warnings about typos and vendor-specific
properties that aren't in the schema.
Signed-off-by: Mike Hansen <mike.hansen@netexperience.com>
- Remove binary executable: tests/config-parser/test-config-parser
- Remove generated test reports: test-report.html, test-report.json
- Update .gitignore to exclude test artifacts and build outputs
These files are generated during build/test and should not be tracked in git.
They will be regenerated when running 'make test-config' or './run-config-tests.sh'.
Related to: OLS-915 Configuration Testing Framework with Property Tracking
Add comprehensive configuration testing framework with property tracking
Implements two-layer validation system (schema + parser) for JSON configurations:
- Add test-config-parser.c with 628-property database tracking implementation status
- Add Python schema validator and property database generation tools
- Add test runner script (run-config-tests.sh) for automated testing
- Add 25+ test configurations covering core and platform-specific features
- Modify proto.c with TEST_STATIC macro to expose cfg_parse() for testing
- Support multiple output formats: human-readable, HTML, JSON, JUnit XML
Enables automated validation of configuration processing, tracks feature
implementation coverage, and provides CI/CD integration for continuous testing.
Signed-off-by: Mike Hansen <mike.hansen@netexperience.com>
