Our company has built a massive logistics platform with more than 100 different screens and components. We’ve never implemented any automated frontend testing because our current workflow seems to work well.
Right now our process is simple: developers build features, business analysts verify requirements are met, then our QA team does thorough manual testing and finds basically every issue. Our testers are really good at what they do and catch bugs we would miss.
I keep thinking maybe we should add automated testing but I’m not sure it’s worth it. Training our developers on unit testing would take time since none of them have done it before. It seems more efficient to stick with our current approach of build, quick manual check, send to QA, then fix any issues they find.
What do you think? Are we missing something important by not having automated tests?
Interesting situation! What happens when your QA team goes on vacation or gets sick though? Also curious - how long does your full manual testing cycle take for bigger features? You might be creating a bottleneck without realizing it.
I’ve been there - manual testing gets crazy expensive once your codebase starts growing. Your QA team’s probably great, but think about the hidden costs. Every tiny change means retesting huge chunks of your app. When deadlines hit, stuff gets skipped and regression testing goes out the window. Automated tests act like a safety net. Your QA folks can focus on exploratory testing and tricky user scenarios instead of boring repetitive checks. Yes, you’ll spend time upfront training developers on unit testing, but it pays off big when you can deploy without sweating and catch bugs before QA even sees them.
you’ll run into scaling probs soon. manual testing gets way harder as you add more features. your QA team does great now, but regression testing will be a huge pain. with 100+ screens, each new feature could break something else. that’s risky!