This is quite bad. It's very visible you don't have any automation work experience or the projects you worked on are as bad as this one More on reddit.com

I'll attempt to answer #3: Language version: make sure you start the new project using Java 21. Familiarize yourself with some of the newer Java language features like records, switch expressions, and text blocks Test reporting: results should be sent to some test case management service or the framework should generate an HTML report with the results. Error handling/logging: Tests should provide screenshots and video recordings of failures. Detailed logging should be present in all areas and the logging level should be configurable Parallel testing: Tests should be easy to run in parallel. The tests should be able to run in any order and not have dependencies on any other tests Backend testing: the tests should have access to the databases/APIs and use them for test data setup/cleanup Clean code: POM pattern is a good start, but you could also look into the screenplay pattern. Also think about other areas you might have duplicate code and come up with ways to eliminate that. For example, you might create domain classes to hold common business logic used in multiple tests. Configuration: environment details and test configuration properties should be stored in some sort of external file like a .properties or .yaml file. It should be simple to run the tests in different target environments. Continuous integration: the tests should be containerized and run in a CI pipeline. It should be possible to start them as one-off job in a CI pipeline. They should also be triggered by PRs/commits in the main application repository. As the number of tests grow, I'd recommend implementing a Selenium Grid to scale the tests more effectively Linting/security scanning: Enforce a consistent code style for your tests with an automated process at check in. Use a tool to manage dependency updates and scan for vulnerabilities for your project More on reddit.com

Totally get the need for a full working example. There are plenty of Selenium + TestNG tutorials out there, but most only cover isolated pieces and skip the real-world structure like parallel runs, reporting, or reusable components. You might want to check GitHub for repos that include Maven project structures with proper page object models, test data management, and CI hooks. Even a simple e-commerce site clone can be a great base for end-to-end flows. Are you mainly looking to understand framework design, or more focused on execution and reporting setup? More on reddit.com

First, selenium is not a framework, is a library. So, with a library you can create your own framework A more straight answer: for python probably robot framework, and for java you can look on selenide More on reddit.com