Testing login, API connectivity, and core features

Use a test customer with sample records. Do not test acceptance, signatures, or ticket submission on real customer transactions without intending those actions.

Connection and session

Confirm that the config endpoint returns JSON, onboarding completes, and login opens the dashboard. Close and reopen the app to check session restoration. Log out and confirm that protected screens are no longer accessible.

Customer records

Open an invoice, estimate, proposal, contract, and project that belong to the test customer. Check totals, dates, statuses, and available PDF downloads against the CRM. Submit a test ticket and reply; confirm that both appear in Perfex.

Test permitted project tasks and discussions. Check a contact with reduced permissions and confirm that restricted actions are denied, including when navigating directly to a record.

Notifications and failures

Register the test device by signing in, then send a push to that test contact. Check foreground and background behavior. Temporarily disconnect the network and confirm that the app provides a recoverable error rather than presenting empty data as a successful response.

Release verification

Repeat the essential checks using a signed release build. Test Android network access, iOS signing, your own Firebase configuration, and the final app name and icons.

Record the app/API versions, CRM/PHP versions, devices, and results. A successful debug launch is only one part of installation verification.

Write Your Comment