test: group scattered operator suites into per-family test files - #427
Merged
Merged
Conversation
The expression-operator tests had accreted one file per operator batch: the numeric family (unary ops, modulo/pow, floor_div, exact Int-Float comparison, Int64 extremes) becomes expr_numeric_test; is_in and is_between become expr_predicates_test; map_batches joins map_elements in expr_map_test; the aggregation family joins the agg entry point in agg_expr_test; lit_series joins the evaluator suite. On the lazy side the Date predicate arm joins the predicate-pushdown rules and the string interaction joins the cross-pass battery; series_stats_test is renamed stats_test to match frame. Tests themselves are untouched - same 1434, same coverage.
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.
The test tree follows the verb-grouping the production tree just got (#426). The expression-operator tests had accreted one file per operator batch; they now live one family per file, each section keeping its own behavioural header:
Cross-surface contracts (reduce equivalence, nullable propagation, N-by-zero shape, property/bench, the per-package assertion smoke files) stay standalone on purpose. Tests themselves are untouched - same 1434, coverage fully covered, mbti and every guard snapshot unchanged.