ABC PAC Module — E2E Test Scripts

E2E-1: PAC Navigation & Permissions

Verify PAC module appears in navigation with correct sub-items and permission levels control access properly for different user roles.

ADMIN NAVIGATION PERMISSIONS CRITICAL PRIORITY

TC-1.1 Verify PAC Module Appears in Navigation with Correct Sub-items HYBRID

Easy 5 min

Preconditions

User has Admin or Chapter Staff Level 2+ permission
User is logged into CHAD2 instance
Navigate to main navigation menu

✓

Navigate to main navigation menu. Verify PAC module appears as top-level menu item between other modules.

Expected: PAC module visible in navigation hierarchy. Menu item labeled "PAC" or "Political Action Committee".

✓

Click PAC module. Verify sub-menu items appear: "PAC Contributions" and "National PAC Summary".

Expected: Two sub-items display under PAC. Both clickable and functional. No additional unexpected items.

✓

Click "PAC Contributions" sub-item. Verify page loads with title "PAC Contributions" and interface displays individual selection, contribution entry form.

Expected: PAC Contributions page loads. Navigation breadcrumb shows PAC > PAC Contributions.

Bug Risk Areas

PAC module not appearing in navigation menu

Sub-menu items missing or incorrectly labeled

Links broken or pointing to wrong URLs

Permission system not hiding PAC from unauthorized users

Related JIRA

ABC-2644

TC-1.2 Verify Permission Levels Control Access to PAC Module HYBRID

Easy 8 min

Preconditions

Admin user has access to User Permissions management
Multiple users with different permission levels exist
Navigate to Admin > Users & Permissions

✓

As admin, create test user with Level 0 permission (no PAC access). Login as test user. Verify PAC module does NOT appear in navigation.

Expected: Level 0 user sees no PAC menu item. Attempt to access PAC via URL returns 403 or access denied.

✓

Elevate test user to Level 1 permission. Login as user. Verify PAC module appears in navigation. Click to access PAC Contributions.

Expected: Level 1 user can see and access PAC module. Page loads successfully.

✓

Test escalating permission levels (Level 2, Level 3). Verify each level grants access. Verify higher levels have same or additional capabilities.

Expected: Permission levels escalate properly. No access gaps between levels. Consistent behavior across all permission levels.

Bug Risk Areas

Permission Level 0 user still able to access PAC

Permission levels not escalating correctly

Inconsistent permission enforcement between UI and API

Related JIRA

ABC-2644

TC-1.3 Verify PAC Module Permission Appears in Chapter Staff Permission Management HYBRID

Easy 6 min

Preconditions

Admin user has access to Chapter Staff management
Navigate to Admin > Chapter Settings > Staff Permissions
Chapter Staff record exists

✓

Navigate to Chapter Settings > Staff Permissions. Click to edit a Chapter Staff member. Verify permission list includes "PAC Module" or similar option.

Expected: PAC permission checkbox/toggle visible in Chapter Staff permission list. Positioned with other module permissions (Contacts, Membership, Events, etc.).

✓

Check PAC Module permission checkbox. Save changes. Verify staff member's account now shows PAC in navigation.

Expected: Permission saved successfully. Staff member can now access PAC module after re-login.

✓

Uncheck PAC Module permission. Save changes. Verify PAC module disappears from staff member's navigation on re-login.

Expected: Permission removed successfully. Staff member can no longer access PAC. URL access attempt returns 403.

Bug Risk Areas

PAC permission not appearing in Chapter Staff permissions list (Regression ABC-2723)

Permission checkbox present but not functional

Permission changes not taking effect until user logs out/in multiple times

Related JIRA

ABC-2644 ABC-2723

E2E-2: Individual Selection & Search

Test type-ahead search for individuals, verify displayed information matches global search data points, and confirm contributions roll up to company level.

USER SEARCH DATA

TC-2.1 Type-ahead Search for Individuals — Verify Results Match Global Search Data Points HYBRID

Easy 8 min

Preconditions

Multiple individuals exist in chapter database
Navigate to PAC > PAC Contributions
Individual Search field visible and ready for input

✓

Click on Individual Search field. Begin typing individual first or last name: "John". Verify type-ahead dropdown appears with matching individuals.

Expected: Dropdown displays individuals with "John" in first or last name. Results appear within 300ms. Max 10 results displayed.

✓

Verify search results include same data points as global search: Individual Name, Job Title, Type, Status, Company, Email, Address. Each result shows relevant data.

Expected: Each dropdown result displays: Name (prominent), Job Title, Company, and optionally Email and Address. Data matches contact database.

✓

Test partial matches and edge cases: Search "Sm" for Smith, search "@example.com" for email domain. Verify results accurate.

Expected: Partial and email searches return correct matches. Case-insensitive matching. No false positives.

Bug Risk Areas

Search results not matching global search data points

Type-ahead dropdown not appearing or slow to respond

Partial or email searches returning incorrect results

Special characters in names causing search to fail

Related JIRA

ABC-2645

TC-2.2 Select Individual — Verify Displayed Information HYBRID

Easy 7 min

Preconditions

Individual search results displayed
Select an individual from search results
Individual detail panel or profile displays

✓

Select an individual from search results. Verify individual detail panel displays with: Name, Job Title, Individual Type, Status.

Expected: Detail panel shows all core fields. Name is prominent. Type and Status are clearly labeled.

✓

Verify additional fields displayed: Company Name, Email Address, Address Information (Company Mailing and Individual Home if available).

Expected: Company field shows company name or link. Email is clickable. Address shows both company mailing and individual home if both exist.

✓

Click individual name or profile link. Verify system navigates to full Individual Profile page with PAC tab available (tested in E2E-5).

Expected: Profile page loads. All individual details visible. PAC tab accessible (may be empty if no contributions yet).

Bug Risk Areas

Required fields missing from detail panel (Name, Job Title)

Company name not displaying or showing incorrect company

Address information incomplete or from wrong address type

Profile link broken or navigating to wrong individual

Related JIRA

ABC-2645

TC-2.3 Verify Individual Contributions Roll Up to Company Level MANUAL

Medium 10 min

Preconditions

Individual is associated to a company
At least one PAC contribution exists for the individual (from E2E-3 tests)
Company Profile is accessible

✓

Navigate to Company Profile (PAC tab). Verify Individual Contributions table displays entries from individuals associated to company.

Expected: Individual Contributions table shows contributions from all company employees. Each row includes: Date, Individual Name, Type, State, Amount, Notes.

✓

Verify individual contribution amounts are reflected in Company PAC Contributions table as rollup totals or individual line items.

Expected: Company-level table shows individual contributions. If rolled up, totals match sum of individual contributions. If individual line items, each shows contributor.

✓

Add new PAC contribution for same individual. Verify contribution appears immediately in both Individual Profile PAC tab and Company Profile Individual Contributions table without page reload.

Expected: Contribution visible in both locations. No refresh delay. Data consistency maintained.

Bug Risk Areas

Individual contributions not appearing in company profile

Rollup totals not calculating correctly

Stale data showing outdated contribution amounts

Individual name incorrectly attributed in rollup table

Related JIRA

ABC-2645

E2E-3: Contribution Entry

Test contribution entry with all required fields, conditional State field, date/amount validation, and chapter-defined defaults.

USER DATA ENTRY VALIDATION CRITICAL PRIORITY

TC-3.1 Enter Contribution with All Required Fields (Type=State) HYBRID

Medium 10 min

Preconditions

Individual selected from search (E2E-2 completed)
PAC Contribution Entry form displayed
Chapter-defined default set to "State" (see E2E-6)

✓

Verify contribution form displays required fields: Date (required), Type (required), State (conditional), Amount (required), Notes (optional).

Expected: All fields present. Required fields marked with asterisk (*). Form is ready for input.

✓

Fill in contribution: Date: today (auto-populated), Type: State (default applied), State: Illinois, Amount: $500.00, Notes: "Legislative district 5 contact".

Expected: All fields accept input. State dropdown shows all US states. Amount accepts currency format. Notes field allows text entry.

✓

Click "Save Contribution". Verify contribution saved successfully. Contribution appears in contribution history table immediately.

Expected: Success message displayed. Contribution added to history table with all entered data. History table refreshed without page reload.

✓

Verify contribution data integrity: Navigate to Individual Profile PAC tab. Verify same contribution appears with correct Date, Type, State, Amount, Notes.

Expected: Contribution visible in profile with all data intact. No truncation or data loss.

Bug Risk Areas

Required fields not validated on save

Currency amount not formatting correctly (e.g., $500 shown as 500.00)

State field not showing all 50 US states

Contribution not appearing in history after save

Contribution not appearing in Individual Profile PAC tab

Related JIRA

ABC-2646

TC-3.2 Enter Contribution with Type=National — Verify State Field Hidden HYBRID

Easy 8 min

Preconditions

Individual selected from search
PAC Contribution Entry form displayed
Type field set to "State" (default)

✓

Verify State field is visible and required when Type = "State". Dropdown shows all US states.

Expected: State field clearly visible with state dropdown populated.

✓

Change Type to "National". Verify State field immediately hides (no page reload required).

Expected: State field disappears from view. No validation error for missing State. Form remains valid for submission.

✓

Fill in contribution with Type=National: Date, Amount, Notes. Leave State empty. Click "Save Contribution".

Expected: Contribution saved successfully without State value. No validation error for missing State. Contribution appears in history with Type=National, State blank.

✓

Toggle Type back to "State". Verify State field reappears and is now required. Cannot save without selecting state.

Expected: State field visible again. Required indicator present. Attempt to save without state shows validation error.

Bug Risk Areas

State field not hiding when Type=National selected

State field still required for National type

State value persisting when hidden (data leakage)

Delayed hiding/showing of State field (poor UX)

Related JIRA

ABC-2646

TC-3.3 Validate Date Field — Default Today, No Future Dates HYBRID

Easy 8 min

Preconditions

PAC Contribution Entry form displayed
Date field is visible and active

✓

Verify Date field auto-defaults to today's date on form load. User does not need to manually select date.

Expected: Date field shows current date (e.g., 2026-04-07). Format clear and consistent.

✓

Click on Date field to open date picker. Attempt to select future date (tomorrow or next week). Verify future dates are disabled (grayed out) in date picker.

Expected: Future dates appear disabled/grayed. User cannot click on them. Only current date and past dates are selectable.

✓

Attempt to manually type future date into Date field (if allowed). Try to save form. Verify system rejects with validation error: "Contribution date cannot be in the future".

Expected: If manual entry allowed, validation error displayed. If manual entry blocked, date input rejected with message.

✓

Select a past date (3 months ago). Verify date picker allows selection. Verify contribution saves successfully with past date.

Expected: Past dates selectable. Contribution saves without error. Date displayed correctly in history.

Bug Risk Areas

Date field not defaulting to today

Future dates not disabled in date picker

Manual entry of future dates allowed and saved

Date validation error message unclear or missing

Related JIRA

ABC-2646

TC-3.4 Validate Amount Field — Positive Only, Currency Formatting HYBRID

Easy 7 min

Preconditions

PAC Contribution Entry form displayed
Amount field is visible and active

✓

Enter positive amount: $1,234.56. Verify amount field accepts currency formatting with commas and decimals.

Expected: Input accepts currency symbols, commas, decimals. Displays formatted: $1,234.56 or 1,234.56 depending on format preference.

✓

Attempt to enter negative amount: "-500" or "$-100". Verify system rejects negative with validation error: "Amount must be positive".

Expected: Negative amounts not accepted. Validation error clear. Field highlighted or error message displayed.

✓

Attempt to enter zero amount: "0" or "$0.00". Verify system rejects with validation error.

Expected: Zero amounts not accepted. Validation error displayed. Field requires amount > 0.

✓

Enter valid amount: $5,000.00. Complete contribution entry and save. Verify amount displays correctly in history: "$5,000.00" or "5000" depending on format.

Expected: Contribution saved. Amount displayed consistently. No decimal/rounding errors.

Bug Risk Areas

Negative amounts accepted and saved

Currency formatting not applied (shows as plain number)

Decimal places truncated or rounded incorrectly

Zero amounts accepted without validation error

Related JIRA

ABC-2646

TC-3.5 Verify Chapter-Defined Default Pre-selects Contribution Type MANUAL

Medium 10 min

Preconditions

Chapter-defined default for PAC type configured (see E2E-6 TC-6.1 or TC-6.2)
Default set to "State" for this test
PAC Contribution Entry form displayed

✓

Load PAC Contribution Entry form. Verify Type field pre-populated with default value: "State" (or configured default).

Expected: Type field shows chapter-defined default on form load. User does not need to manually select. Default is respected.

✓

Verify State field appears automatically when form loads with default Type=State (conditional field logic). State field is visible and required.

Expected: State field visible when Type default is State. Conditional logic applied correctly on form load.

✓

User can still change Type from default: Change from State to National. Verify State field hides, form is valid without State.

Expected: Default is not locked. User can override. Form adapts to user selection.

✓

Change chapter-defined default to "National" (via Chapter Settings). Load new PAC Contribution Entry form. Verify Type field now pre-populated with "National". State field hidden.

Expected: Default change takes effect immediately. New contributions default to National. Setting changes applied consistently.

Bug Risk Areas

Chapter-defined default not applied to form

Conditional State field logic not respecting default

Default setting change not taking effect for new contributions

Old contributions affected when default is changed (should not happen)

Related JIRA

ABC-2648

E2E-4: Contribution History

Test contribution history table display, default sorting, and filtering capabilities.

USER REPORTING DATA VIEW

TC-4.1 Verify History Table Shows All Contributions with Required Columns HYBRID

Easy 8 min

Preconditions

Individual selected with multiple contributions (from E2E-3 tests)
Contribution History section displayed below contribution entry form
At least 3 contributions exist for individual

✓

Verify Contribution History table displays all contributions created in prior tests. Table header shows columns: Date, Type, State, Amount, Notes.

Expected: All required columns visible. Column headers clear. All contribution rows displayed (no missing entries).

✓

Verify Date column shows dates in consistent format (e.g., MM/DD/YYYY). Verify Type shows "State" or "National". Verify State shows state abbreviation (e.g., "IL") or full name.

Expected: Date format consistent and readable. Type displays correctly (State/National). State column shows abbreviation or full state name.

✓

Verify Amount column shows currency formatted values (e.g., $500.00 or 500.00). Verify Notes column shows note text (truncated with ellipsis if long).

Expected: Amount currency-formatted. Notes visible (truncate if > 50 chars). All data intact in table.

Bug Risk Areas

Missing columns in history table (Date, Type, State, Amount, Notes)

Contributions not appearing in history

Date format inconsistent or unreadable

Notes truncated incorrectly or overflowing table

Related JIRA

ABC-2647

TC-4.2 Verify Default Sort by Date (Most Recent First) HYBRID

Easy 6 min

Preconditions

Contribution History table displayed with 3+ contributions
Contributions have different dates (past dates)

✓

Verify history table is sorted by Date column in descending order (most recent first) by default. First row should have most recent date.

Expected: First contribution row has today's or most recent date. Subsequent rows have earlier dates. Descending sort indicator visible on Date header.

✓

Click Date column header. Verify sort toggles to ascending (oldest first). Click again, verify sort returns to descending (newest first).

Expected: Column header clickable. Sort toggles between ascending/descending. Sort indicator (arrow) updates. Table re-orders on click.

✓

Click on other column headers (Type, Amount). Verify table can be sorted by those columns. Verify Date remains default sort when page reloads.

Expected: All columns sortable. Default sort (Date desc) restored on page reload or when returning to page.

Bug Risk Areas

Default sort not by Date

Sort direction reversed (oldest first by default)

Sort not toggling on column click

Sort indicator missing or unclear

Related JIRA

ABC-2647

TC-4.3 Test Filters (Contribution Type, State, Date Range) MANUAL

Medium 12 min

Preconditions

Contribution History table displayed with mixed contributions (State and National, various states)
Filter controls visible above or near history table

✓

Verify filter controls present: Contribution Type dropdown, State dropdown, Date From/To fields.

Expected: All filter controls visible and labeled. Dropdowns/fields accessible. Filter button or auto-apply logic present.

✓

Set Contribution Type filter to "State". Verify history table immediately shows only State-type contributions. National contributions hidden.

Expected: Filter applied instantly or after "Apply" button. Table updates. Count reduced to match State contributions only.

✓

Set State filter to "Illinois". Verify history shows only Illinois contributions. Other states hidden.

Expected: State filter applied. Only IL entries visible. Table refreshed.

✓

Set Date range: From: 3 months ago, To: 1 month ago. Verify only contributions within date range displayed. Contributions outside range hidden.

Expected: Date filter applied. Only contributions in range visible. Date fields accept picker or manual entry.

✓

Apply multiple filters: Type=State, State=Illinois, Date range. Verify all filters combined (AND logic). Only entries matching all criteria displayed.

Expected: Filters combine correctly. Results show only Illinois State contributions within date range. Clear filter option available.

Bug Risk Areas

Filters not appearing or labeled incorrectly

Filter changes not applying to table

OR logic used instead of AND (incorrect filter combination)

Date range picker not functioning

Filter state not persisting on page reload

Related JIRA

ABC-2647

E2E-5: Profile Integration

Test PAC tab in Individual and Company profiles, including PAC history display and dues renewal integration.

USER PROFILES INTEGRATION

TC-5.1 Individual Profile — PAC Tab Displays After Committees & Groups Tab HYBRID

Easy 6 min

Preconditions

Individual record exists in system
Navigate to Individual Profile
Verify profile tabs visible (Summary, Contacts, Committees & Groups, etc.)

✓

Navigate to Individual Profile. Verify tab list includes: Summary, Contacts, Committees & Groups, PAC (new tab).

Expected: PAC tab visible in tab navigation. Positioned after Committees & Groups tab. Tab is clickable.

✓

Click PAC tab. Verify PAC tab content displays. If individual has no contributions, display empty state message or empty table.

Expected: PAC tab loads. Shows "No contributions yet" or empty table. Tab content is distinct from other tabs.

✓

Verify tab label is clear: "PAC", "PAC Contributions", or similar. Icon or visual indicator optional but helpful.

Expected: Tab label is clear and consistent. Matches PAC terminology used elsewhere in system.

Bug Risk Areas

PAC tab not appearing in Individual Profile

PAC tab positioned before Committees & Groups (incorrect order)

PAC tab not clickable or content not loading

Related JIRA

ABC-2650

TC-5.2 Individual Profile — PAC History Table Shows Correct Columns and Data MANUAL

Medium 10 min

Preconditions

Individual has at least 1 PAC contribution (from E2E-3)
Navigate to Individual Profile > PAC tab

✓

Click PAC tab. Verify PAC history table displays with columns: Date, Contribution Type, State, Amount, Notes.

Expected: All required columns visible. Column headers clear. Same columns as main PAC Contributions history table.

✓

Verify table displays all PAC contributions for this individual. Each row shows: Date (formatted), Type (State/National), State (if applicable), Amount (currency formatted), Notes (text or truncated).

Expected: All individual contributions visible. Data matches what was entered in PAC Contributions interface. No data loss or corruption.

✓

Verify table sorted by Date descending (most recent first). Click Date header to toggle sort. Verify sort works.

Expected: Default sort by Date desc. Column sorting functional. Sort indicator visible.

✓

Make new PAC contribution via PAC Contributions interface (E2E-3). Navigate to Individual Profile PAC tab. Verify new contribution appears immediately in table.

Expected: New contribution appears without page reload. Data consistency between PAC interface and Individual Profile.

Bug Risk Areas

PAC history table missing columns

Data not displaying or showing incorrect contributions

New contributions not appearing in profile until page refresh

Currency formatting inconsistent between interfaces

Related JIRA

ABC-2650

TC-5.3 Company Profile — PAC Tab with Company & Individual Breakdown Tables MANUAL

Medium 12 min

Preconditions

Company has at least 1 associated individual with PAC contribution
Navigate to Company Profile
PAC tab exists in company profile tabs

✓

Click PAC tab on Company Profile. Verify two tables displayed: Company PAC Contributions and Individual Contributions.

Expected: Two distinct tables visible. Each table clearly labeled. Separate headers and data sections.

✓

Verify Company PAC Contributions table shows columns: Date, Contribution Type, State, Amount, Notes. Displays direct company-level PAC contributions.

Expected: Company-level contributions displayed separately. Not including individual contributions. Only direct company PAC entries.

✓

Verify Individual Contributions table shows columns: Date, Individual Name, Contribution Type, State, Amount, Notes. Displays contributions from all individuals associated to company.

Expected: Individual breakdown table shows all employee contributions. Individual name column is prominent. Includes both manual PAC contributions and dues renewal PAC lines.

✓

Verify both tables sorted by Date descending by default. Both tables support filtering. Verify data accuracy and no duplication between tables.

Expected: Both tables sorted consistently. No overlap or duplicate entries between company and individual tables. Filtering works on both.

Bug Risk Areas

PAC tab missing from Company Profile

Individual Contributions table not showing individual-level PAC entries

Individual Name column missing from breakdown table

Duplicate entries between company and individual tables

Related JIRA

ABC-2651

TC-5.4 Company Profile — Dues Renewal PAC Lines with State from Additional Lines MANUAL

Medium 15 min

Preconditions

Company has dues renewal PAC additional lines (in Membership & Dues module)
State field toggled ON in Chapter Settings (E2E-6 TC-6.3)
PAC additional line has State selected (e.g., Illinois)
Navigate to Company Profile > PAC tab

✓

Verify Company PAC Contributions table includes entries from dues renewal process. Each dues PAC line appears as: Type="State", State=from additional line State, Notes=from additional line Description.

Expected: Dues PAC lines appear in Company PAC Contributions table. Type always "State" (per business rule: dues always state PAC). State pulled from additional line state field. Notes from Description field.

✓

Verify manual PAC contributions and dues renewal PAC lines both appear in Company Contributions table. No duplication. Each type clearly distinguishable if needed.

Expected: Both manual and dues PAC entries in same table. Can be distinguished by date/amount or comment indicating source. No duplicates.

✓

Create new dues renewal with PAC additional line. Toggle State ON for PAC line, select State="Texas", add Note. Navigate to Company Profile PAC. Verify new dues PAC line appears correctly.

Expected: New dues PAC line appears in Company PAC Contributions. Type=State, State=Texas (from additional line), Notes from Description. Data reflects latest dues renewal.

✓

Regression Test (ABC-2867): Verify State field for dues additional lines NOT hardcoded as NULL. State value correctly pulled from additional line State column, not defaulting to NULL.

Expected: State field populated correctly for dues PAC lines. No NULL values. All state selections respected. Bug ABC-2867 resolved.

Bug Risk Areas

Dues renewal PAC lines not appearing in Company PAC tab

State values hardcoded as NULL instead of pulling from additional lines (Regression ABC-2867)

Notes field showing empty instead of additional line Description

Dues PAC lines appearing as "National" instead of "State"

Related JIRA

ABC-2651 ABC-2867

E2E-6: Chapter Settings & Defaults

Test chapter-defined PAC defaults and State field settings for dues additional lines.

ADMIN CONFIGURATION SETTINGS

TC-6.1 Chapter-Defined Default — Set PAC Type to State, Verify Default Applies HYBRID

Easy 8 min

Preconditions

Admin user with access to Chapter Settings
Navigate to Admin > Chapter Settings > PAC Configuration

✓

Navigate to Chapter Settings > PAC Configuration or similar section. Locate Chapter-Defined Default PAC Contribution Type setting.

Expected: PAC configuration section found. Default PAC Type setting visible with options: State, National.

✓

Verify current setting. If not already "State", select "State" from dropdown. Click "Save" or "Update".

Expected: Setting saved successfully. Confirmation message displayed. No errors on save.

✓

Navigate to PAC > PAC Contributions. Click to add new contribution for individual. Verify Type field pre-populated with "State" (not "National").

Expected: Type field defaults to State. No manual selection required. Default applied immediately.

✓

Verify State field appears automatically when Type=State default applied. Conditional logic working correctly.

Expected: State field visible and required when Type=State default applied. Form ready for contribution entry.

Bug Risk Areas

PAC Configuration section not found in Chapter Settings

Default setting not saving correctly

Default not applying to new contribution forms

State field not conditional on default Type=State

Related JIRA

ABC-2648

TC-6.2 Chapter-Defined Default — Set to National, Verify Default Applies HYBRID

Easy 8 min

Preconditions

Admin user with access to Chapter Settings
Navigate to Admin > Chapter Settings > PAC Configuration
Default currently set to "State" (from TC-6.1)

✓

Navigate to Chapter Settings > PAC Configuration. Change Chapter-Defined Default PAC Contribution Type to "National". Click "Save".

Expected: Setting changed to National. Saved successfully. Confirmation displayed.

✓

Navigate to PAC > PAC Contributions. Click to add new contribution. Verify Type field pre-populated with "National" (changed from previous default).

Expected: Type field defaults to National. Default change takes effect immediately for new contributions.

✓

Verify State field is hidden when Type=National default applied. State field only shows when user changes Type to "State".

Expected: State field not visible with National default. Conditional logic working. User can toggle Type to show/hide State field.

✓

Verify setting change does NOT affect historical contributions. Navigate to Company/Individual Profile PAC tabs. Verify contributions created under old default (State) still show Type=State with state values intact.

Expected: Historical data unchanged. Only new contributions default to National. Setting changes forward-only.

Bug Risk Areas

Default setting not changing to National

New contributions not using updated default

Historical contributions changing when default changed (data integrity issue)

State field still showing when Type=National (should be hidden)

Related JIRA

ABC-2648 ABC-2773

TC-6.3 Chapter Settings — Toggle State Field for Dues Additional Lines ON/OFF HYBRID

Easy 10 min

Preconditions

Admin user with access to Chapter Settings
Navigate to Admin > Chapter Settings > Additional Dues Settings & Tools
Setting default is OFF

✓

Navigate to Chapter Settings > Additional Dues Settings & Tools. Locate setting: Include State Field for Dues Additional Lines.

Expected: Setting found in Additional Dues section. Toggle or checkbox visible. Default OFF (unchecked).

✓

Toggle setting to ON. Click "Save". Verify setting saved successfully.

Expected: Setting enabled (checked). Saved without error. Confirmation displayed.

✓

Navigate to Membership & Dues > Add/Edit Dues Renewal. Verify State field now appears in Additional Lines section (for PAC and all other additional lines). Field is optional.

Expected: State dropdown appears in Additional Lines for dues entry. User can select state or leave empty. Field optional (not required).

✓

Toggle setting back to OFF. Save. Navigate to Dues entry. Verify State field disappears from Additional Lines. No state option available for PAC additional lines.

Expected: State field hidden when setting OFF. Additional lines show without state option. Setting toggle works both directions.

Bug Risk Areas

State field setting not found in Chapter Settings

Toggle not functioning or not saving

State field appearing in Dues Additional Lines regardless of setting

State field marked as required instead of optional

Related JIRA

ABC-2649

TC-6.4 Verify Setting Changes Only Affect Future Data, Historical Data Unchanged MANUAL

Medium 12 min

Preconditions

Existing PAC contributions with various states and types in system
Chapter-Defined Default set to "State"
State field for Dues Additional Lines currently ON

✓

Record baseline: Navigate to Company Profile PAC tab. Note existing contributions: Types, States, Amounts. Screenshot or document current state.

Expected: Baseline recorded. All existing contributions visible with current data.

✓

Change Chapter-Defined Default from "State" to "National" (TC-6.2). Change Dues State field setting from ON to OFF (TC-6.3).

Expected: Both settings changed and saved. New contributions will use National default. Dues additional lines won't have state option.

✓

Verify historical PAC contributions NOT affected by setting changes. Navigate to Company/Individual Profiles PAC tabs. Compare current data to baseline. All Type, State, Amount values unchanged.

Expected: Historical contributions retain original data. No retroactive changes. Setting changes are forward-only.

✓

Add new PAC contribution. Verify Type defaults to "National" (new setting). Add new Dues renewal with additional lines. Verify State field NOT visible for PAC additional line (new setting OFF).

Expected: New contributions follow updated defaults. New contributions use National PAC type. Dues PAC additional lines lack state option. No impact on historical data.

Bug Risk Areas

Historical contributions changed when settings updated (data integrity violation)

Old dues additional lines losing state values when setting turned OFF

Setting changes not taking effect for new data

No clear indication that setting changes only affect future data

Related JIRA

ABC-2648 ABC-2649