Beta testing

How to test FretTrack

Beta testing is most valuable when it follows real repair-shop work. Use realistic workflows, record what happened, and report confusing behavior as clearly as possible.

What to test

  • Login, shop access, and approved-account behavior.
  • Customer creation, search, and returning-customer selection.
  • New job intake, instrument details, priority, and promise date.
  • Photos, damage maps, serial-number images, and customer report selection.
  • Work logs, status changes, parts, services, scheduling, and reports.
  • Inventory parts, vendors, purchase orders, receiving, barcode labels, and purchase history.
  • Roles such as owner, admin, tech, and viewer.

How to record results

Use the workbook for normal testing. Mark each item as Pass, Fail, Blocked, Not Tested, or Needs Clarification. Use severity to show how much the issue affects the shop workflow.

For longer bugs, use the Bug Log sheet and include links to screenshots, videos, or issue references.

What to include in a bug report

  • What screen or workflow you were using.
  • What you clicked or entered.
  • What you expected to happen.
  • What actually happened.
  • Your browser, device, and shop role.
  • Whether it happens every time.
  • Screenshot or video when helpful.

Where to send feedback

Use the in-app Report Issue button when available. For login, public-site, or account-access problems, email support@frettrack-app.com.

If you received a separate beta feedback channel with your invite, use that channel as well.