🚀 Feedback Request: Help Shape the Future of Docker-Selenium! 🚀

[VietND96]

Feature and motivation

Hey everyone! 👋

As the Docker-Selenium project continues to grow, we’re not just looking at the open issues and feature requests—we’re also working to prioritize the use cases and features that matter most to the community. This project provides a simple way to run Selenium Grid with Chrome, Firefox, and Edge using Docker, supports deployment to Kubernetes for autoscaling browser nodes, and offers utilities to make the Grid more functional.

One key focus is making Docker-Selenium a reliable tool for browser automation in CI/CD workflows, streamlining test execution, and improving the overall testing experience.

We’d love your feedback to ensure we’re heading in the right direction. Here’s what we’d like to know:

1️⃣ What are you currently using Docker-Selenium for?
• Are you running tests locally or leveraging the orchestration platform for scalability?
• What’s working well for you, and what’s not?

2️⃣ Which use cases and features should we prioritize?
• What functionality do you find critical or wish Docker-Selenium supported?
• Are there any utilities or integrations you think would make it more efficient?

3️⃣ How does Docker-Selenium fit into your CI/CD workflows?
• Does it simplify your automation process?
• Are there any blockers or areas for improvement?

4️⃣ Would a survey help?
• Would you participate in a survey to share your use cases and feature requests?

Your insights are crucial to help us focus on the right priorities and deliver value to the community. Please drop your thoughts in the comments, or feel free to open an issue or discussion on the GitHub repo.

Thanks in advance for helping us make Docker-Selenium even better! 🙌

Usage example

N/A