This project is gone, and I'm too exhausted to configure the outdated versions of Chrome, Selenium, and Cucumber. This project has far too many problems. It was the final time I could run it with the project attached. I use playwright now; sorry, dumb selenium.
- This framework for automation in checking Website using Selenium, Cucumber and Junit 4. You can reach me.
- The framework has following features:
- Modular Design
- Maven based framework
- Log4j2 enabled for logging
- Report Generation (Extent-reporting)
- Helper class to handle web component such as (Button, Wait,... etc)
- Using gherkin to develop feature files
- Centralized Configuration (Using Properties file)
- POM
- LOMBOK
- Page Factory
- Screen shot at the end of every scenario
⚠️ NoteWhat is automation in testing? The Web is abuzz with talk about “automated testing” and “test automation”. Automation comes with a tasty and digestible story: eliminate “manual testing”, and replace messy, complex humanity with reliable, fast, efficient robots! Testing can not be automated and automate all your test cases does not give you a full status of your product. Heuristics of GUI Automation Tools give you a better approach to automation. The Round Earth model guides you what you need to spend your effort for automation in testing.
What is BDD? You are trying to automate test cases with a supporting tool to write some tests with human natural language, BDD does not look like that. You should Learn about BDD, VisualTest and Approval Testing, it will help you what is BDD and how to use it correctly. Andy Knight has written a Better behavior-driven development: 4 rules for writing good Gherkin.
- You can open the RunnerTest on src\test\java\runners and change the feature you want to execute, but I recommend you run it by the command line. It enables us to run in different test execution strategies and, also in a pipeline, that is the repo purpose.
mvn -Dtest=RunnerTest test
Over view:
Detail page:
Screeshot of a scenario:
