Skip to content

[PR1-B005-TC08] Corrupted UserDefaults priority data is handled gracefully on app launch #41

Description

@jsingh6

Test Case PR1-B005-TC08 — Corrupted UserDefaults priority data is handled gracefully on app launch

Field Value
Priority P1
Behavior PR1-B005
Type error_state
PR of origin #1

Preconditions

  • App is installed
  • At least one todo exists with a valid priority saved in UserDefaults

Steps

  1. Using a device file manager or debug tool, manually corrupt the priority field in the UserDefaults plist for an existing todo (e.g., set it to an unexpected string or invalid type)
  2. Launch the app
  3. Navigate to the todo list
  4. Observe the affected todo item

Expected Result

The app does not crash. The affected todo is either shown with a safe fallback/default priority or displays an appropriate error state. Other todos with valid data are unaffected.


Filed automatically by TIP M3 pipeline. Pool entry: harness/test-cases/. TC ID: PR1-B005-TC08.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions