with you
Create project and catalogue
Add sections, groups and check items in the editor or upload a finished list. Items can carry CRITICAL, PLAN or iOS.
Test plans that collect themselves.
Build a question catalogue, invite testers by link. The results come to you on their own.
A test round without testr looks like this
- Testplan_v4_final.xlsxJonas
- RE: RE: Who takes section 5?Aylin
- Testplan_v4_final_Marta_corrected.xlsxMarta
- Re: Item 3.2 doesn’t work for meLena
- FW: New version of the spreadsheetTobias
- RE: Which version is current?Jonas
One status for everyone4 of 5 testers done, 2 bugs reported
One status while everyone tests
Five testers work at the same time. Every answer lands in the matrix right away, so there is nothing to collect.
| Check item | LenaHartmann | JonasBrenner | AylinDemir | MartaRuiz | TobiasKern |
|---|---|---|---|---|---|
| The admin shows only the sign-in form on first visit, no project data behind itSign in | |||||
| Signing in with a valid email and password opens the admin, your own name appears in the top barSign in | |||||
| A wrong password is rejected with a message and the form staysSign in | |||||
| An unknown email address is rejected without revealing whether the account existsSign in | |||||
| Signing in with an empty password field is rejectedSign in | |||||
| After closing and reopening the browser you are still signed inSign in | |||||
| Signing out returns to the sign-in form, going back in the browser shows no more dataSign in | |||||
| “Register for free” opens the form for a new accountCreate account |
works
doesn’t work
can’t be tested
Example with real check items from the testr catalogue
What goes away
Four steps are left, and none of them is an email.
Until nowWith testr
Build a spreadsheet and send it as an attachment
Create project and catalogue
Sections, groups and check items in the editor, or upload a finished list.
Asking around who takes which part
Invite testers
Name and email are enough. Everyone gets a link and sees only their sections.
Getting five versions back
Let them check off
Testers click each item into one of three columns. Saving happens instantly.
Copying answers together
Evaluate
Key figures, bugs with comment and reporter, the item-by-tester matrix.
What an invitation link looks like
Every tester gets their own. That is all they need.
testr.software/testr/the test sheet page#from here on, everything stays in the browserp=3F6C2A10-8B4Ethe project&t=9d41f0c2b7e3this tester’s access
The browser never sends what comes after the # to the server. Project and access therefore show up in no log and no referrer.
Where the link travels
Four stops, and at none of them do you have to forward anything.
with you
Invite testers
Name and email are enough. The email carries the project name in the subject and the personal link. You can also copy the link and pass it on yourself.
with the tester
Open and check off
No account, no installation. The tester sees only their sections and clicks each item into one of three columns. Every entry goes out right away.
back with you
See the status
Key figures, reported bugs with comment and reporter, the item-by-tester matrix. The filter “only contradictory ratings” shows what depends on the device.
A look inside
Five tabs for you, a single page for your testers.
What the tester sees
Their name, their progress and the items. They only enter device and app version, the rest is clicked off in three columns. A bug opens the comment field, and a screenshot fits too.
Invite testers
Name, email, done. The list shows ok, bug, can’t be tested and open per tester, plus buttons for link, resending the email and blocking.
The results
How much is checked, what was reported and who rated which item how. The filter “only contradictory ratings” shows what depends on the device.
The question catalogue
Move, edit and tag sections, groups and items. It saves on its own and counts the version.
What you get
Plans differ in size. Everything here works in every plan.
Three answers per item
Works, doesn’t work, can’t be tested. The last two open a comment field.
Saves in the background
Without a connection the state stays in the browser and is sent later.
Assign sections
A tester sees only their sections.
Own scenarios
Testers add their own cases per section.
Catalogue versions
Running sheets stay valid when the catalogue grows.
Invitation by email, and that was the last one
Subject with the project name, personal link. After that you don’t have to write to anyone. You can also copy the link yourself.
Export as JSON
The whole state as one file. Your data stays your data.
Stored separately
Every account has its own folder. Tester data cannot be fetched over the web.
from Premium
Testers who sign up themselves
The landing page gives a project a public sign-up page. You share one link, people sign up, and you decide who tests.
Set up the page
In the Landing page tab: description, test period, contact address and the maximum number of open applications. Save, and the link is ready.
Sign up
Applicants enter name and email, device and experience if they like, and give consent. They don’t need an account.
Confirm the address
The application only shows up for you after the click in the confirmation email. You get a notification.
Approve
In the Testers tab you approve and assign sections. The applicant gets the usual invitation with their link. Rejecting deletes the application without a message.
Reachable only through the link. The page appears in no listing and cannot be guessed.
Renew the link. A new key, and the old link leads nowhere. The project stays as it is.
No access before approval. An application does not open a test sheet.
Your quota stays free. The tester limit only counts when you approve. Unconfirmed applications expire after seven days.
For your testers, it’s just a link
- No account, no installation. Open it and start, on a phone or a computer.
- Nothing to send back. Every answer goes out right away, a screenshot of a bug too.
- Carry on whenever it suits. The link always leads back, from another device too.
Pricing
You pay for scope. Cancel monthly, no setup fee.
0 €forever
Free
For trying it out and for a small project that stays small.
- 1 project
- 3 testers
- 25 check items
- Help through documentation
19 €per month
Premium
Several test rounds a year, a team testing along.
- 10 projects
- 25 testers
- 250 check items
- Sign-up page
- Email, reply next working day
49 €per month
Premium Plus
Agencies and departments with several projects at once.
- 25 projects
- 50 testers
- 500 check items
- Sign-up page
- Email, reply next working day
199 €per month
Enterprise
When projects and testers are past counting.
- unlimited projects
- unlimited testers
- unlimited check items
- Sign-up page
- Dedicated contact, setup included
The public sign-up page, where testers apply themselves, is available from Premium.
Frequently asked
Do my testers need an account?
No. A tester opens their link, that is all. Project and access sit after the # in the address, and the browser does not send that part to the server. Only whoever creates test plans needs an account.
How do testers get in through the landing page?
They sign up on the sign-up page and confirm their address. You then see the application in the Testers tab and approve it. Only then do they get their link to the test sheet.
What happens when I reach a limit?
Existing projects and sheets carry on, nothing is lost. You can only create something new again once you switch plan or delete an old project. Check items count per catalogue: 25 in the one project on Free, 250 in each of the ten on Premium.
Can I switch between plans?
At any time, in both directions. When downgrading, all projects are kept. You can only create new ones once you are below the new limit.
Where is the data kept?
On the server, in a folder of its own per account. The files holding testers’ names and email addresses cannot be fetched over the web, only the server itself reads them. Permission is checked on every request, not just at sign-in.
What if a tester works offline?
The sheet carries on and keeps everything in the browser. As soon as there is a connection again, the state goes out. Closing the page with unsaved work makes the browser warn.
Can I change the catalogue mid-run?
Adding works at any time. Rewriting or deleting an item takes the reference away from an answer already given. It then shows up in the results as “item no longer in the catalogue”. During a run, better to add.