SaaS ideas your next customers are already looking for
100 SaaS startup ideas for the people who said they'd pay, from agency owners to dentists. Micro SaaS ideas, AI SaaS ideas and B2B SaaS ideas: find yours, build it, sign them up.
Popular:
| # | Idea |
|---|
No idea matches this filter.
Pain points in business: what people struggle with
Search the problems to solve, as people described them on Reddit and other platforms, in their own words.
Popular:
| # | Pain point |
|---|
No pain point matches this filter.
Brittle E2E Test Maintenance
End-to-end tests break constantly due to brittle selectors and UI changes, forcing costly manual maintenance and eroding trust in automation.
In their words
maybe we shouldn't rewrite a mature suite solely because maintaining selectors sucks
intelligent and consistently named screenshots would be ideal now for a speedy process and easy import into x-ray and jira
this is the hardest problem when you can't add your own test IDs
That class does not need a human and used to eat whole evenings.
Ich bräuchte jemanden der tests schreibt um meine beweiskette zu härten . Hab ich da überhaupt ne Chance?
We have also seen that this issue should have been caught by our unit tests but we have mocked everything so the case in question never got flagged.
So we manually test things on the browser, and write Excel documents for test cases, and take screenshots of every result from a test case. Tiring and painful.
My app has just gotten bigger than what I can manually check
Getting releases out the door recently has required babysitting CI test runs for an entire day to get all tests to pass.
someone breaks the suite, but no one stops developing or merging
A false green gets merged, included in the report and shown to management as "automation coverage".
you're not looking at "did this pass," you're looking at "did this pass on attempt 3."
I basically want an industry standard practice implemented on my team of 4 devs who are too busy doing other things.
it still failed silently in production because the fix was real but pointed at the wrong asset. Nothing in the process ever complained.
QA and dev teams
Where they talk
- r/QualityAssurance
- r/Playwright
- r/softwaretesting
- r/AI_Agents
- r/webdev
- r/Everything_QA
- r/ExperiencedDevs
- r/ProgrammerHumor
Tools they use today
- Playwright
- Claude
- Cypress
- Appium
- Selenium
- Askui
- Chrome
- Codex
Why those fall short
- unit tests mocked everything; e2e regression testing lacks traction
- PHPUnit and Pest were learned but never adopted in development
- manual checking no longer covers integrations, billing, permissions, devices and OS versions
- no unit or integration tests; Playwright used for individual components
- AI cannot replicate gut-feeling edge case discovery
Map of ideas
Drawing the map…