Org Web Adapter

Editing hungryroot/jira/be_7350_add_auto_refund_support_to_createtestcustomerview_test_endpoint.org

:PROPERTIES:
:ID:       b868881e-f2ca-4d62-90c3-92e83af34a7e
:END:
#+title: BE-7350 Add auto_refund support to CreateTestCustomerView test endpoint

- source :: https://hungryroot.atlassian.net/browse/BE-7350
- tags   :: [[id:3a477c02-e26d-40f7-a719-0aa1cd169dd8][Hungryroot API Project]] 
- epic   :: [[id:86327fb4-0f66-4bc6-9068-c414cea77042][EP-411 Eng Parking Lot]]
- sprint :: [[id:9821b605-4d59-432e-b15d-95999d25cc39][HR BE Sprint 106]]
- status :: [[id:87ee4162-0c60-41e4-8863-89e3ca8bf2f5][Status - Code Review]]
        
* Tasks
** DONE Add auto_refund support to the CreateTestCustomerView :project:work:hungryroot:cursor:ep411:sprint106:be7350:
:PROPERTIES:
:ID:       5691383b-424a-2ac0-0965-e8f5a04f5a09
:END:
<2026-03-25 Wed>

* Description

** Background

The CreateTestCustomerView in test_automation/views/create_test_customer.py is
used to create test customers with configurable settings for QA and testing
purposes. Currently, there is no way to control whether an order's
can_auto_refund property returns true or false through the test endpoint.

** Problem

Testers need the ability to force auto_refund to return true or false when
creating test customers through the test automation endpoint, so they can test
flows that depend on auto-refund eligibility without manually manipulating the
underlying data.

How can_auto_refund Works

The Order.can_auto_refund property (in app/models/order.py) evaluates to True
when ALL of the following conditions are met:

Order status is in OrderStatus.SubmittedStatuses

customer.no_auto_credit is False

The order has no refunds (refund == 0)

The number of issue-credit log events is below the dynamic config threshold
(AUTO_ISSUE_CREDIT_EVENTS_RESTRICTION)

** Proposed Implementation

Add an auto_refund boolean field to TestCustomerCreationSerializer that controls
whether can_auto_refund will return True or False for the customer's orders:

auto_refund=true (or omitted/default): Ensure customer.no_auto_credit = False
(default behavior, auto-refund eligible)

auto_refund=false: Set customer.no_auto_credit = True on the created customer,
which causes can_auto_refund to return False for all of their orders

This maps to the existing Customer.no_auto_credit boolean field, which is the
most direct and reliable way to control auto-refund eligibility at the customer
level.

** Acceptance Criteria

[ ] New optional auto_refund boolean field added to
TestCustomerCreationSerializer

[ ] When auto_refund=false, the created customer has no_auto_credit=True

[ ] When auto_refund=true or omitted, the created customer has
no_auto_credit=False (default)

[ ] The field is documented in the API schema via help_text

[ ] Unit tests cover both auto_refund=true and auto_refund=false scenarios