Repository navigation
test(google): guard DataOps contract test selection - #34
Merged
Merged
Conversation
alexeygrigorev
force-pushed
the
wt-1d9cf506-harness-guard
branch
from
November 3, 2026 17:32
776c857 to
7c92d03
Compare
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
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.
This stacked follow-up hardens the synthetic DataOps contract harness after the pinned PR 307 consumer renamed its dry-run test.
Changes:
CSV importer dry-run contract preserves raw amount precision and formatted datestitle.Validation on this branch:
PYTHONPATH=. pytest -q plugins/google/tests/test_google_data_pull.py: 5 passed, 1 skipped.python3 .agents/skills/google-data-pull/run_dataops_contract.py: pinned DataOps Node dry-run 1 passed; Dapier exporter tests with the DataOps checkout 6 passed.5de43419c7e1ce890f4e11e083c68a9cf76e9ec6.Base this PR on Dapier PR #33's branch so this remains a separate reviewable follow-up. Do not merge or deploy; the parent PR remains open.