A planned 75% cut in test time: the engineering behind Labster's virtual-lab scale-up
As education moved online, Labster had to expand virtual science learning fast while keeping quality high. Over a 12-month scale-up, 11 Rollout IT specialists supported portal development, LMS integrations, and test automation, including a parallelization plan to cut test time by up to 75%.
Scaling an education platform while classes are already running? Talk to us
Snapshot
| Field | Detail |
|---|---|
| Client | Labster |
| Industry | EdTech / virtual science labs |
| Region | Denmark-based, global education reach |
| Company stage | Established EdTech scaling during the online-learning surge |
| What we built | Senior engineering and QA for portal, backend, LMS integrations, and test automation |
| Tech stack | VueJS, ReactJS, Node.js, TypeScript, Contentful, Gridsome, JAMstack, SSG, Quasar |
| Time-to-value | 12-month collaboration (per source) |
| Headline KPIs | 11 professionals – 6+ months frontend contribution – automated tests – planned 75% test-time reduction via parallelization |
The challenge
Labster's virtual labs became even more important as education shifted online. The company needed to ramp development quickly, standardize access to a growing set of solutions, and support learning-management-system integrations. New features arrived week by week, which made automated testing essential for a live education product where a failure can interrupt a real class in progress.
Why Labster chose Rollout IT
Labster needed senior specialists it could add dynamically, including backend engineers, frontend engineers, and automated and manual QA testers. The collaboration fit Labster's remote-first culture and let internal teams add capacity during a high-pressure growth period, without the ramp-up cost of building that depth from scratch.
The solution
Rollout IT professionals contributed across the Labster ecosystem. On the frontend, the team worked with VueJS, TypeScript, and the Quasar framework on the Learning Management Portal, the interface connecting students and teachers to Labster services. On the backend, work focused on microservice communication: the team reviewed the codebase, reduced repetition, and introduced SDK packages so services could share consistent interfaces, which supported a more standardized platform as Labster's modules multiplied.
LMS integration was another major area: the team connected third-party learning systems, including Google Classroom, to the new portal while protocol updates and the portal backend moved in parallel. QA specialists built automated testing protocols for new features and later joined LMS integration testing, with a parallelization plan projected to cut test time by up to 75%. Faster, automated testing is what lets an education platform keep shipping without risking the classes already relying on it.
Results
- Labster gained 11 Rollout IT professionals across engineering and QA during a 12-month scale-up.
- Portal and LMS integration work supported a more unified learning experience.
- Automated testing protected quality as new features shipped frequently.
| Metric | Before | After | Timeframe |
|---|---|---|---|
| Scale-up capacity | Rapid online-learning demand | 11 Rollout IT professionals added | 12 months |
| Platform access | Solutions accessed in different ways | Learning Management Portal standardization | Engagement period |
| Backend consistency | Repetition across services | SDK packages and shared interfaces | Engagement period |
| Test execution | Manual risk during frequent changes | Automated protocols; parallelization planned to cut time up to 75% | QA phase |
The AI angle
No AI capability is claimed for this story. The value is remote science education at scale: engineering and QA capacity helped the platform keep growing while protecting the learner experience.
What's next
This is the technical deep-dive behind Labster's scale-up: the portal, LMS integrations, and test automation under the hood. As the QA workflow matures, the next step is to validate the actual time saved by parallelized test execution.
Related case study: Weekly releases sustained through global expansion tells the business-outcome side of the same Labster partnership.
FAQ
How did Rollout IT support Labster's scale-up? With 11 senior engineering and QA specialists across the Learning Management Portal, backend microservices, LMS integrations, and test automation, over 12 months.
What was the impact on testing? Automated testing protocols were built, with a parallelization plan projected to cut test time by up to 75%.
Which LMS integrations were involved? Third-party learning systems including Google Classroom.
What was it built with? VueJS, ReactJS, Node.js, TypeScript, Contentful, Gridsome, JAMstack, SSG, and Quasar.
Add the engineering and QA capacity that keeps learning stable during growth. Talk to us.