Projects & collaboration
Beta testing
Clients and their testers report bugs with screenshots
Run a beta of a website or mobile app with your clients. Invite a client by email, let them add their own testers, and collect bug reports with screenshots, steps and device details in one place.
Open Beta testing
Opens in RIO. You will be asked to sign in if you are not already, and you see it when your role allows.
What Beta testing is
Beta testing lets you hand a website or app to a client for testing and collect their bug reports in one place.
You invite a client by email. They add testers from their own team, and everyone reports bugs, feedback and suggestions with screenshots and device details.
Your team sets the status of each report and can turn it into a task in the linked project.
At a glance
- Programs for websites, mobile, desktop and other apps
- Clients from any email address, no account needed
- Clients add and remove their own testers
- Test sign-in details testers can copy
- Bugs, feedback and suggestions with severity and status
- Screenshots and files by drag and drop or paste, viewed full screen
- Comments on every report from both sides
Points left Guideline
Story points left each day against a straight guideline to zero. Velocity shows points finished per sprint.
From Projects, elsewhere in Projects & collaboration.
What it does
Set up a program
- Programs for a website or web app, a mobile app, a desktop app or something else
- Links to the builds or sites to test, and notes on what to test
- Test sign-in details that testers can copy, with passwords hidden until shown
- Close a program when testing ends and reopen it if needed
People
- Colleagues as managers or testers
- Clients from any email address, with a personal link and no account
- Clients add and remove testers from their own team
- Send a new link or remove someone, and their old link stops working
Reports
- Bugs, feedback and suggestions with severity from low to critical
- Steps to reproduce, page or screen, device, operating system, browser and app version
- Up to 10 screenshots and files per report, by drag and drop or paste, viewed full screen
- Statuses New, In progress, Fixed, Won’t fix and Closed, set by managers
Follow-up
- Comments on every report from both your team and the client side
- Filter reports by status, severity, type and who reported them, or search by title or number
- Create task makes a task in the linked project from a report
What you get
Reports you can act on
Each report arrives with steps, device details and screenshots instead of a vague email.
The client runs their own testers
Clients invite their own team without waiting on you.
Bugs flow into delivery
A report becomes a task in the project, so it gets fixed and tracked with the rest of the work.
How to use Beta testing
Step 1: Create a program
Press New program, give it a name, choose the project and platform, add the links and describe What to test.
Step 2: Add test sign-in details
Under Test sign-in details, add the test accounts testers will need. Everyone in the program can see them.
Step 3: Invite your client
On the Testers and clients tab, enter the client’s name and email and press Invite client. They get a personal link by email.
Step 4: Add colleagues
On the same tab, choose a colleague and a role, Tester or Manager.
Step 5: Collect reports
Testers press Report a bug, fill in what happened and the steps, and paste or drop screenshots.
Step 6: Triage
On the Reports tab, open each report, set its status, comment, and press Create task to put it in the project.
Step 7: Close the program
When testing ends, press Close program on the Details and sign-in tab. Everyone can still read the reports.
Who it’s for
Teams that build websites and apps for clients, and the people testing them.
Hand a build to a client
Add the link and test sign-in details; the client invites their own team to test.
Reports you can act on
Each report has severity, steps, device and screenshots pasted straight from the clipboard.
Turn bugs into tasks
Create a task in the linked project from any report and track its status.
How Beta testing connects
Beta testingconnects to 1 app
CRMContractsSitesOnline storeWebsite testingFinanceBooksInventoryPoint of salePurchasingPracticeIT assetsPeopleMy SpaceRecruitPayrollShift staffingHelp deskBookingsPortalsKnowledge baseProjectsMessagesSignCalendarVaultReviewBeta testingFormsAutomationAnalyticsAdminCreatorWorks with
Plans
Checking which plans include it…
Good to know
What Beta testing does not do today.
- Files are limited to 10 per report or comment, up to 10 MB each.
- Reports become tasks only when the program is linked to a project.
- Only managers, administrators and owners can create programs.
Questions
Do clients and their testers need an account?
No. Each person opens a personal link sent by email.
What can a client see?
Only their own program, its reports and comments, and the display names of the people in it.
Who sets the status of a report?
The program’s managers. The person who reported it can still edit its details.
What happens when a program is closed?
Everyone can still read it, but testers and clients cannot add reports or comments until it is reopened.