01The organization
Imagine an EdTech company whose learning platform is used by a few hundred school districts. Teachers build courses and quizzes, students submit work on school laptops and phones, and parents follow grades in an app.
Traffic and stakes peak in the first week of term and during exams. A broken quiz timer in exam week becomes a support crisis and a renewal risk.
EdTech QA runs to the school calendar. Most new features land over the summer, most traffic arrives in the first weeks of term, and every role, from teacher to student to parent, sees the same data differently. Testing has to be ready before the bell, not after the first support ticket.
02Business objectives
- Turn each term's new requirements into tests quickly
- Test teacher, student and parent roles separately
- Cover the browsers schools actually use
- Run a full readiness suite before each term
03Testing challenges
Requirements pile up
New features arrive as long requirement documents, and writing test cases from them takes weeks.
Three roles, one record
Teachers, students and parents see the same grade differently, and permissions must be exact.
Browser mix
Students use school laptops, home browsers and phones.
Seasonal peaks
Most of the year's risk lands in a few weeks.
04Before and after
How the testing work would change once the journeys run in Robonito.
- Test design
- Today:Weeks spent turning requirement documents into test cases.
- With Robonito:Draft test plans generated from documents and Jira epics, then reviewed.
- Roles
- Today:Permissions spot-checked with one or two accounts.
- With Robonito:Teacher, student and parent journeys run on every release.
- Devices
- Today:Tested on the team's own laptops.
- With Robonito:Key journeys run across major browsers and both apps.
- Term start
- Today:A long manual checklist in the last week of summer.
- With Robonito:A full readiness suite run before each term.
05How Robonito would test it
- 1
Plans from requirements
The Test Planning Agent turns requirement documents and Jira epics into test plans the team reviews and edits.
- 2
Role-based journeys
Tests log in as teacher, student and parent to check each view of the same course.
- 3
Across browsers
Key journeys run across major browsers and on the student and parent apps.
- 4
Term readiness
A full suite runs from GitHub Actions before each term, with failures raised in Jira.
06Test scenarios, in plain language
Tests you'd write in Robonito on day one. Each one is typed as written; the agent works through the app and saves the steps.
- QuizzesAs a teacher, create a 10-minute quiz with ten questions; as a student, submit at nine minutes; confirm the grade appears in the gradebook.
- DeadlinesSubmit an assignment a day after the due date and confirm it is marked late with the course's penalty applied.
- Parent accessLog in as a parent and confirm only their own child's grades are visible.
- EnrollmentUpload a class roster of 30 students and confirm all 30 appear in the course.
- BrowsersOpen the course page in Chrome, Safari and Edge and confirm the assignment list loads in each.
- MobileMark an announcement as read in the student app and confirm it shows as read on the web.
07What the pilot measures
No made-up numbers: a pilot measures these against your current baseline, on your own app.
Time from requirement to test
Days from a new requirement to a reviewed test plan.
Role coverage
Share of features tested for every role.
Term-start incidents
Support tickets in the first week of term, before and after.
Readiness run
Time to run the full term readiness suite.
08Rolling it out: the first month
A realistic plan for a team starting from zero, with the baseline comparison built in.
- Week 1
Generate the plan
The Test Planning Agent turns the term's requirement documents and Jira epics into a draft test plan the team reviews.
- Week 2
Build the role journeys
QA writes quiz, assignment and gradebook journeys for teacher, student and parent accounts.
- Week 3
Go cross-browser and mobile
Key journeys run across major browsers and on the student and parent apps.
- Week 4
Rehearse term start
GitHub Actions runs the full readiness suite, and the team tracks first-week tickets against last term.
09Frequently asked questions
Can Robonito generate tests from requirement documents?
Yes. AI Studio can generate tests from requirement documents, Jira stories and epics, Swagger or OpenAPI definitions and the live app. The team reviews and edits the result before it runs.
How do we test different user roles?
Write a journey for each role, such as teacher, student and parent, and check what each one can see and do on the same course. Role tests run with the rest of the suite.
Does Robonito test across browsers?
Yes. The same journey runs across major browsers in parallel, so a browser-specific break shows up before students hit it.
Which plan suits an EdTech team?
Web testing is on every plan. If you also need the student and parent apps tested, mobile testing is on Pro at $199 a month, which includes 1,000 test cases a month and 5 parallel runs.