You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
tabletest: Ambiguity policy for writing tests from a feature description — proceed with the most reasonable interpretation and record assumptions and open questions in @Description, rather than stopping to ask clarifying questions
tabletest: Worked example for collapsing an optional-field parameter object (constructor, setters, or builder) into a single map column with a @TypeConverter supplying defaults
tabletest: "Let tables drive the API decomposition" — if a row needs a helper fabricating raw data to reach a derived input value, target a narrower function; cheap rows signal a well-placed table
tabletest: Conversion workflow now finishes the migration — replace the old framework's matchers, remove its imports and build-file dependencies (with matching quality check)
tabletest: Value-set guidance covers both axes — grouping same-outcome values within a row and collapsing duplicate rows for interchangeable inputs; every tier expressed as one row including both boundary values
Changed
tabletest: Quality checks tightened — no if/switch/ternary in test methods including null-guards (defaulting belongs in a @TypeConverter or helper); a lone error/null/empty case belongs as a table row with a Throws? column, not a separate @Test; date cutoffs prefer descriptive relative values or a cutoff column