Aglet

Verify Boolean Import Values and Invalid Tokens

Verification should compare explicit boolean meaning, not just successful parsing. Use independently specified token expectations and inspect the saved state. Include a nonempty false token and invalid text, because both can expose a conversion that appears correct for ordinary true examples while assigning unintended values to other source strings.

Check whether the outcome improved

  1. Exercise the accepted token contract

    Import each documented true and false form with supported case and whitespace variations. Compare exact saved booleans and preview interpretations. Keep a false word that is nonempty in the fixture so the check detects generic truthiness rather than merely proving that an empty string can be converted to false.

  2. Check missing and invalid behavior

    Try blanks and unsupported words under the documented field rules. Confirm they are rejected, left unchanged, or assigned an explicit default only where that behavior is intended. Where updates exist, begin with known state so an unchanged value can be distinguished from an accidental fallback to true or false.

  3. Inspect the resulting workflow

    Reopen the imported record and exercise a representative filter or state display that consumes the boolean. Compare that behavior with the intended source meaning. Confirm the correction does not invert another accepted token or hide an invalid input behind a valid-looking destination state and a generally successful import summary.

What to carry forward

Accept when documented tokens retain their meaning and missing or invalid values follow the explicit contract through preview, persistence, and representative use. Record untested field-specific defaults separately. A passing true example alone does not verify false strings, unknown tokens, or the behavior of an update with missing input.

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