proper testing before browser extension releases

[tessus]

Select Topic Area

🚫 Product Feedback

Code Contribution Proposal

I was wondering, if the dev team could use proper testing before releasing the browser extensions.
Currently I am too afraid to automatically update the extension.

2025.7.0 rendered the browser unusable. 2025.7.1 improved the situation slightly, but it's still not as snappy and resource-conscious as 2025.6.x.

Dumb side question: why is the faulty commit not reverted until a proper fix is found and implemented?

2025.8.0 has reports that auto-fill does not work anymore. Hmm, this is the most basic functionality of the extension, yet the dev team didn't catch this?

I am not trying to bash the devs, although they certainly deserve some scolding. There are testing tools available, like Playwright. Wouldn't it be possible to add such tests to verify that at least the most basic things work?

[github-actions[bot]]

Thank you for your contribution! GitHub Discussions is specifically for proposing code that you would like to write for the Bitwarden codebase. Since this post does not appear to include a proposal, it will be closed. If you believe this was done in error or have any questions, please feel free to reach out to us!

• 💡 For feature requests and general discussions, please visit the Bitwarden Community Forums.
• ℹ️ For questions and support, visit the Bitwarden Help Center.
• 🐛 To report a potential bug, please visit the appropriate repository: Server | Clients | iOS | Android.

[tessus]

If that is the case, please remove the Product Feedback option, if you just close them automatically anyway. Or do you enjoy to mock the community?

Additionally this discussion is to propose adding proper tests. Which is code. Apparently not for the bitwarden devs.