3 ms·
The testing burden is already enormous for things people want sites tested for.
by MattGaiser 6y ago
The testing burden is already enormous for things people want sites tested for.
- thanksforfish 6y agoWhats the solution for the busy engineer? Anyone know a Selenium plug in that let's you run with browser extensions or something? There's too many popular extensions to test manually.
- MattGaiser 6y agoThis is probably so far down the list that I would be interested to hear of any kind of testing of extensions at all for non-extension companies.
- enjoylife 6y agoHaven't seen this automated, but I have seen internal issues raised by folks within large orgs when their extension started breaking things. But it's only once you have 50+ to 100's of engineers working on a product, each with a subset of extensions installed, that you can rely on the cross product of engineers and their installed extensions for realistic coverage.
- MattGaiser 6y agoI've never worked on a team of more than 7 on a product, so even testing on Firefox is considered too much work for testing. Put in dollars, it probably costs 5-10 million a year (if not more) to test extensions even haphazardly.
- edoceo 6y agoI feel like I could get pretty far building this, with that budget.
- clintonb 6y agoFollow this guide: https://support.1password.com/compatible-website-design/ https://support.1password.com/compatible-website-design/. Even if you can't test, at least try. I find that few forms take the basic steps. Most importantly: don't fuck with paste!
- deleted 6y ago[deleted]
- murermader 6y agoI mean what is there to test, really? Just use the the different input types and mark your fields as "email", "password" and so on. There is nothing to test really. If a password manager does not work when given clear hints / type description of what is expected, then that is the fault of the password manager.