- Регистрация
- 1 Мар 2015
- Сообщения
- 1,481
- Баллы
- 155
The Problem We All Face
As developers, we've all been there: You build a feature that looks perfect on your machine, only to have a user report that it's completely broken on their iPhone 8, or in Firefox, or on a tablet.
I've spent countless hours manually checking websites across different browsers and devices, yet bugs still slip through to production. It's frustrating, time-consuming, and honestly feels like a problem that should be solvable in 2025.
The Current Landscape
There are several approaches to this problem, each with drawbacks:
1. Manual testing
2. Full UI automation frameworks (Cypress, Playwright, etc.)
3. Browser stacks and device clouds
4. Visual regression tools
For smaller projects or indie developers, the overhead of setting up comprehensive testing often feels disproportionate to the project size. But skipping testing altogether leads to quality issues.
A Potential Solution: Testplot
I've been exploring building a browser extension called Testplot that automatically detects responsive design issues and browser compatibility problems without requiring test scripts.
The concept is simple:
No test writing required. No expensive subscriptions. Just immediate feedback on potentially problematic areas.
I Need Your Input
Before diving deeper into building this, I'd love to hear from other developers:
I've created a brief survey (takes ~3 minutes) to collect insights here:
I'll be sharing the aggregated findings with everyone who participates, as I believe the entire community can benefit from understanding these challenges better.
Let's Discuss
Have you found any effective solutions for this challenge? Do you have suggestions for how such a tool should work? I'd love to hear your thoughts in the comments!
As developers, we've all been there: You build a feature that looks perfect on your machine, only to have a user report that it's completely broken on their iPhone 8, or in Firefox, or on a tablet.
I've spent countless hours manually checking websites across different browsers and devices, yet bugs still slip through to production. It's frustrating, time-consuming, and honestly feels like a problem that should be solvable in 2025.
The Current Landscape
There are several approaches to this problem, each with drawbacks:
1. Manual testing
Pros: Simple to start, no setup required
Cons: Extremely time-consuming, error-prone, and impossible to be comprehensive
2. Full UI automation frameworks (Cypress, Playwright, etc.)
Pros: Comprehensive, can catch many issues
Cons: Significant setup time, maintenance overhead, flaky tests
3. Browser stacks and device clouds
Pros: Real device testing
Cons: Expensive, still requires manual checking or test script writing
4. Visual regression tools
Pros: Can catch UI changes automatically
Cons: Setup cost, many false positives, subscription fees
For smaller projects or indie developers, the overhead of setting up comprehensive testing often feels disproportionate to the project size. But skipping testing altogether leads to quality issues.
A Potential Solution: Testplot
I've been exploring building a browser extension called Testplot that automatically detects responsive design issues and browser compatibility problems without requiring test scripts.
The concept is simple:
Install the extension
Browse your website
Get alerts for potential responsive design breakpoints, compatibility issues, and interactive element problems
Generate reports you can address
No test writing required. No expensive subscriptions. Just immediate feedback on potentially problematic areas.
I Need Your Input
Before diving deeper into building this, I'd love to hear from other developers:
How much time do you typically spend on manual testing?
What are your biggest pain points when testing across devices and browsers?
Would a tool like this be valuable to you?
I've created a brief survey (takes ~3 minutes) to collect insights here:
I'll be sharing the aggregated findings with everyone who participates, as I believe the entire community can benefit from understanding these challenges better.
Let's Discuss
Have you found any effective solutions for this challenge? Do you have suggestions for how such a tool should work? I'd love to hear your thoughts in the comments!