Systems | Development | Analytics | API | Testing

This is the sixth and final post in our "Features Sitting Idle" series, where we shine a light on OctoPerf features that are already in your account, ready to save you hours every week. It's a quiet but recurring friction. Teams that test regularly all end up with a preferred report layout. But in practice, that structure is often rebuilt manually after each run, or lost entirely when moving between projects.

The OctoPerf web application is a large Angular workspace: 7,786 TypeScript files, around 381,000 lines of code, 1,166 components and 2,738 test files. We have just taken it from Angular 20 to Angular 22, deleted zone.js, and replaced Karma and Jasmine with Vitest. The interesting part of this story is not the version number. It is that we got the strategy wrong first. We spent months migrating the codebase component by component, drowned in manual regression testing, and still let bugs reach production.

This is the fifth post in our "Features Sitting Idle" series, where we look at OctoPerf features that are already in your platform but often missed by the teams that would benefit the most. This one is for IT teams running OctoPerf on-premise. IT teams managing an on-premise OctoPerf instance regularly run into the same friction around SSO.