Historian conformance: assert DurationGood/DurationBad in ProcessedConformance #840

Closed
opened 2026-11-11 03:27:27 -05:00 by dohertj2 · 1 comment
Owner

#820 added DurationGood/DurationBad (ms) to the SqlServer/QuestDb backends with unit coverage and the QualityMix datasets. The shared ProcessedConformance suite does not yet assert them per backend; add them so a backend regression is caught by the same oracle as the other 19 aggregates.

#820 added DurationGood/DurationBad (ms) to the SqlServer/QuestDb backends with unit coverage and the QualityMix datasets. The shared `ProcessedConformance` suite does not yet assert them per backend; add them so a backend regression is caught by the same oracle as the other 19 aggregates.
dohertj2 added the type:testpriority:p3 labels 2026-11-11 03:27:27 -05:00
Author
Owner

Done (7095e128). Pushed to master in d1b6cad2. ProcessedConformance asserts DurationGood/DurationBad (hand-computed + vs Percent × interval + SDK comparison + edge cases). Live: SqlServer 211/211, QuestDB 249 + 1 skip.

Done (`7095e128`). Pushed to master in `d1b6cad2`. `ProcessedConformance` asserts DurationGood/DurationBad (hand-computed + vs Percent × interval + SDK comparison + edge cases). Live: SqlServer 211/211, QuestDB 249 + 1 skip.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: dohertj2/lmxopcua#840