Check out BongoBd.com website automation.
TestCase 01: (Drama & Sports Test) Test-1
- Go to BongoBd.com URL
- From menu bar click Drama
- Search 420
- From 420 drama list ,play 1st drama.
- Unit Testing Done.
Test-2
- Go to BongoBd.com URL
- From menu bar click Sports
- Search messi
- From list, play 3rd news, pause & play.
- Check Unit Testing.
TestCase 02: (Movie Test) Test-1
- Go to BongoBd.com URL
- From menu bar click Music
- Scroll Down & go to latest music.
- Play 4th movie.
- Check Unit Testing.
TestCase 03: (Movie Test) Test-1
- Go to BongoBd.com URL
- From menu bar click Movies
- Scroll Down & go to tribute to salman shah.
- Play 1st movie.
- Check Unit Testing.
This project using the following languages and frameworks:
- Java 11 as the programming language
- TestNG as the UnitTest framework to support the test creation
- Selenium WebDriver as the web browser automation framework using the Java binding
We know that any automation project starting with a good test architecture. This project can be your initial test architecture for a faster start. You will see the following items in this architecture:
- Page Objects pattern
- Execution types
- BaseTest
- Configuration files
- Profiles executors on pom.xml
- Pipeline as a code
- Video Play and Pause automation
Do you have any other items to add to this test architecture? Please do a pull request or open an issue to discuss.
I will not explain the Page Object pattern because you can find a lot of good explanations and examples on the internet. Instead, I will explain what exactly about page objects I'm using in this project.
This class has a protected constructor to remove the necessity to init the elements using the Page Factory.
Also, it sets the timeout from the timeout
property value located on general.properties
file.
All the Page Object classes should extend the AbstractPageObject
.
It also tries to remove the driver
object from the Page Object class as much as possible.