Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary\n\nAdds volume and freshness anomaly detection tests to
stg_ordersandstg_paymentsto improve upstream coverage for the criticalcpa_and_roasmodel.\n\n### Tests Added\n\nstg_orders:\n-elementary.volume_anomalies— Detects sudden drops or spikes in order volume that would silently distort CPA/ROAS calculations.\n-elementary.freshness_anomalies— Catches stale order data before it causes misleading marketing performance metrics.\n\nstg_payments:\n-elementary.volume_anomalies— Monitors payment record volume to prevent undercounting revenue.\n-elementary.freshness_anomalies— Ensures payment data stays current to maintain accurate ROAS reporting.Created by:
joost@elementary-data.com