Ctrl K
Frontend · Senior · System design

Design a testing strategy for a large frontend application that has almost no tests, where releases regularly break key user flows.

~10 min by voice

How to approach it

This checks whether the candidate can build a system of release confidence from scratch: prioritize by business risk, spread checks across test levels, wire them into CI and keep maintenance costs under control, rather than just 'raising coverage'.

Have you seen this question in a real interview?
Answers0
Avg. score—
Strong—
Practiced0
Topics
Similar questionsHow do you set up testing for a service that works with a database, a message broker and a couple of external APIs? What do you test at which level? SeniorWhat tests would you write for a backend service, and how is a unit test different from an integration test? JuniorYou've joined a project as tech lead: three hundred thousand lines of Python, the tests take forty minutes, and half the team doesn't run them locally. How would you rebuild the testing strategy? SeniorWhat kinds of tests are used in frontend development, and how do they differ from each other? JuniorHow do you test backend code that works with a database: do you mock the repositories or spin up a real database? Mid-level

Answer by voice

The interviewer will ask this question and listen. Think out loud and ask for a hint if you need one. When you're done, pause or tap “That's my answer”. In about a minute, your score and the points you covered show up here.

Sign in to answer

Best with headphones · ~10 min