Aglet

Verify Decimal and Grouping Separators in Imports

Verification should compare numeric meaning across source formats while checking presentation separately. Use a known expected magnitude for each fixture and preserve the source string beside it. A successful import or a well-formatted display does not establish that a decimal separator was interpreted under the correct convention.

Check whether the outcome improved

  1. Exercise supported numeric conventions

    Import equivalent values using each documented decimal and grouping style. Include fractions, negatives, integers, and punctuation inside quoted CSV fields. Compare the actual numeric results with independent expectations, including a case where an incorrect interpretation would still produce a valid number and escape ordinary type validation.

  2. Verify format choices and ambiguity

    Where a numeric-format selection exists, confirm its preview interpretation survives execution. Exercise ambiguous strings under the documented rule and inspect the warning or rejection where a choice is required. Keep unsupported mixed conventions explicit rather than accepting a file simply because individual cells can each be guessed differently.

  3. Check storage and subsequent use

    Reopen the imported value and compare a representative calculation or export with the intended magnitude. Distinguish changes in display punctuation from changes in value. Confirm the correction did not strip legitimate grouping, reverse a sign, or alter the fractional part of another supported numeric format.

What to carry forward

Accept when the supported format matrix preserves magnitude from source through storage and representative use. Record unresolved ambiguity and untested producers separately. A display-only check remains incomplete when the actual parsed number or the confirmed format’s handoff to execution has not been observed.

Technical background: Google Cloud documentation.

Keep the decision with the work.

Use a Work Item in Aglet to record the problem, the evidence you have, and the next decision. Add an owner and priority, then keep updates in the discussion so the next person can follow the reasoning.

Create an account See the product workflow