Detach opencart demo site related testing from automation UI project and include multiple QA members to do testing
demo.opencart.com
https://trello.com/b/MVdb3O1a/weekend-project-automation-ui-selenium
https://drive.google.com/drive/folders/0Bzvlm2T8LMb1N2ktem9qTU8xRUE?usp=sharing
- Test Steps -> Reusable test steps, all are test
- Workflows (group of test steps preset for testing)
- Tests, for specific purposes 4. Groupped Tests 5. Tests Suits.
Libs:(gradually Increments) Selenium-java Junit Allure-Junit SL4J AspectJ
Running The tests : Maven Test Run ->Locally ->From Jenkins or any CI (for CLI support , there will be an entry from Program -> main method) ->With Webdriver Remote Driver execution
Fork it. Create a branch (git checkout -b myBranch) Commit your changes (git commit -am "Added feature") Push to the branch (git push origin myBranch) Create a new Issue with a link to your branch, or just make a Pull Request.
I will enrich more scripts so that it is useful to support more typr of angular apps
-
Single Module Maven Project to minimize complexity
-
Cucumber intregration (optional, open for discussion)
-
Allure Integration (optional, open for discussion)
Testing Open cart site
Dwnload driver and put in driver folder (which will be used in property)
Currently, code is out dated
- Selenium
- Webdriver Manager
- To test : mvn test, mvn verify
- To Run
- Allure report : need to specify style
- Maven failsafe
- Cucumber
-create a folder for reports in project root (src lavel)
- Remote Driver management
- Yandex Element
- Selenide
- Local Remote Driver
- Test Case in Allure
- Jenkins test jobs