Thanks for joining the Parish Hall QA blitz. We're doing a focused pass through the entire platform before we onboard our first design partners. Your job is to break things, find friction, and flag anything that would embarrass us in front of a real church admin.
What is Parish Hall?
A modern church management platform (ChMS) covering congregation management, groups, service planning, events, giving, pastoral care, and a member-facing portal.
Daily standups: Post a short async update in #parish-hall-qa-blitz each morning — what you tested yesterday, what you're testing today, and any blockers. Flag blockers immediately; don't wait for standup.
How to Submit Bugs & Enhancements
Option A — In-App (Preferred)
Click the bug icon in the top-right header bar inside the app. This auto-captures your current route, session replay link, browser, and environment. Fill in:
Title — short, specific summary
Category — Bug, Feature Request, Question, or Other
Severity — see guide below
Description — steps to reproduce, expected vs. actual, screenshots
Option B — Jira Direct
File at PARISHSUP Service Desk. Include: numbered repro steps, expected vs. actual behavior, screenshot or Loom, and browser + viewport (desktop vs. mobile).
Severity Guide
Critical — Data loss, auth bypass, core workflow completely broken
High — Feature broken but workaround exists
Medium — Incorrect behavior, doesn't block the workflow
Low — Cosmetic, copy, minor UX polish
What Counts As What?
Bug — Something is broken, crashes, shows wrong data, or doesn't complete a workflow
UX Friction — It works but is confusing, slow, or takes too many clicks
Enhancement — A missing feature or capability you'd expect a church admin to need
Blocker — You literally cannot proceed with testing a module. Post in Slack immediately.
Schedule — Parallel Coverage
Each tester covers different modules simultaneously so we get full platform coverage. All testers converge on Day 1 (onboarding) and Day 5 (cross-cutting + regression).
Day
Tester A
Tester B
Tester C
1
All Testers
Auth, Signup, Onboarding, Invite & Join Flows
2
A Congregation — People & Households
B Groups & Meetings
C Events, Calendar & Check-in
3
A Services & Scheduling
B Songs & Song Library
C Giving & Statements
4
A Pastoral Care & Notes
B Member Portal (as member role)
C Settings, Roles & Permissions
5
All Testers
Cross-cutting (Cmd+K, notifications, reports, mobile), regression on fixed bugs
Tip: Don't save bugs for the end of the day. File as you find them so the dev team can start triaging in parallel.
Progress Tracker
Check off each item as you complete it. Progress saves automatically to your account.
Overall Progress
0/ 0
1 Auth & Onboarding
Day 1
Sign up as a brand-new user and complete church onboarding
Log out and log back in — verify return to /admin
Invite a new person via email — sign up with invite link
Invite someone who already has a Parish Hall account
Join code flow (/join) — valid code
Join code flow (/join) — invalid code
Password reset / forgot password
Login & signup on mobile viewport
Edge: signup URL while already logged in
Edge: expired or malformed invite token
Edge: redirect loops between auth states
Edge: multiple tabs with different auth states
2 Congregation — People & Households
Day 2 · A
View people list — search and filter by name, status, membership
Add a new person with all fields
Edit an existing person's profile
View person detail — profile, activity timeline, notes
Archive a person — verify removed from active list
Restore an archived person
Bulk actions: select multiple, change status or add tags
Export people to CSV
Saved segments: create, apply, edit, delete
Create a new household with members and roles
Edit household details (address, name)
Move a person between households
View household detail page
Edge: person with minimal info (first + last only)
Edge: special characters in names (O'Brien, hyphenated)
Edge: archive last member of a household
Edge: search by preferred name vs. legal name
3 Groups & Meetings
Day 2 · B
View groups list
Create a new group (name, description, type, schedule)
Add members to a group
Remove a member from a group
View group detail — members, meetings, attendance tabs
Generate meeting occurrences from schedule
Take attendance for a meeting
RSVP flow from the member portal
Set member schedule preferences / exceptions
Edge: group with no members — meeting flow
Edge: delete a group — meeting history?
Edge: person in 3+ groups — profile shows all?
4 Events, Calendar & Check-in
Day 2 · C
View calendar (month and week views)
Create a one-time event
Create a recurring event
Edit event — date, time, location, description
View event detail and take attendance
Create and manage event types / categories
Cancel single occurrence vs. all future
Quick-create event from calendar view
Check-in kiosk: child check-in
Check-in kiosk: visitor registration
Edge: edit one occurrence vs. the series
Edge: event spanning midnight or multiple days
Edge: far-future and far-past calendar navigation
Edge: overlapping events on same day
5 Services & Scheduling
Day 3 · A
View services/plans list
Create a new service plan (date, type, service times)
Add items to the plan (songs, notes, headers)
Drag-and-drop reorder plan items
Assign team members to roles/positions
Use a template to create a plan
View plan detail — order of service, assignments, notes
Print / export service plan (PDF)
Teams list — create team, add members with positions
Schedule tab — view who's serving when
Edge: assign someone with a schedule conflict
Edge: plan with no songs or no team assignments
Edge: duplicate a service plan
Edge: reorder items on mobile viewport
6 Songs & Song Library
Day 3 · B
View the song library
Search by title, artist, tag
Add a new song (title, artist, key, tempo, tags)
Add an arrangement with chord chart
View song detail — arrangements, usage, tags
Add a song to a service plan from the library
Transpose a song to a different key
View and print a chord chart
Edge: songs with no arrangements
Edge: special characters in titles or lyrics
Edge: system/shared vs. org-specific songs
7 Giving & Statements
Day 3 · C
View giving dashboard
Record a manual donation (cash/check)
Create a batch, add donations, close it
Online giving: Stripe test card (4242 4242 4242 4242)
Set up recurring giving
View a person's giving history from profile
Generate and view giving statements
Email a statement to a donor
View giving reports and totals
Edge: anonymous donation (no person)
Edge: refund or void a donation
Edge: statement for zero-giving person
Edge: multiple funds on single donation
8 Pastoral Care & Notes
Day 4 · A
Add a pastoral note to a person's profile
View notes on activity timeline
Edit and delete a note
View the journey/pipeline board
Create a journey template (steps, assignments, timing)
Move a person through journey steps
Assign a follow-up task to a staff member
Edge: note with very long content
Edge: journey template with no steps
Edge: person in multiple active journeys
9 Member Portal
Day 4 · B
Portal dashboard — view as member
View and edit own profile
View household info
View group memberships, RSVP to meetings
Online giving from portal
View giving history / download statements
Notification preferences
Church directory (if enabled)
Edge: member with no household
Edge: full portal on mobile viewport
Edge: member accessing /admin routes (should block)
10 Settings, Roles & Permissions
Day 4 · C
Update church name, logo, contact info
Invite a staff member, change role, remove access
Toggle modules on/off — verify sidebar nav updates
Custom field options (congregation fields)
Billing / subscription settings
Notification preferences (admin)
Edge: disable module with data, re-enable, data preserved?
Notifications: bell icon, notification center, read/unread
Reports: attendance, engagement, giving
Theme toggle: light, dark, system
Mobile responsive: every major page at phone width
Report Issue button — submit and verify on /admin/feedback
Re-test all bugs marked as fixed during the week
Edge: slow network / throttled connection
Edge: rapidly switching between modules
Edge: browser back/forward through nested routes
Edge: app open in two tabs simultaneously
Testing Tips
Test the happy path first, then try to break it. Complete the workflow as intended before exploring edge cases.
Try both desktop and mobile for every module. Resize your browser to phone width or use Chrome DevTools device mode.
Test with real-ish data. Don't just use "test" and "asdf" — use realistic names, addresses, and amounts. Data display issues only surface with real content.
Pay attention to loading and empty states. What happens before data loads? What does a page look like with zero records?
Check form validation. Submit blank forms, exceed character limits, use invalid email formats, enter negative numbers.
Watch for data consistency. After creating or editing something, does it show correctly on list views, detail views, and related pages?
Note anything that surprises you, even if it technically "works." If you had to think about what to do next, that's UX friction worth filing.