- Project Description
- Project Structure
- Project Structure Explanation
- User Stories and Test Scenarios
- Test Coverage Table
- Tools and Technologies
- Project Team
- GitHub Repository
- Project Team GitHub
- License
This project was developed to automate test scenarios on the E-Junkie demo shopping site.
The tests are written using TestNG, Selenium WebDriver, and the Page Object Model (POM) structure.
Tests are executed via the testng.xml configuration file.
✅ Features:
- Designed using POM architecture
- Scenario management via
testng.xml - Parallel and cross-browser test support
🔗 E-Junkie Demo Site
🔗 E-Junkie Main Page
EJunkieProject/
│
├── src/
│ ├── eJunkie/
│ │ │
│ │ ├── base/ # BaseDriver and core structure
│ │ ├── elements/ # Page Object classes (POM)
│ │ ├── methods/ # User actions
│ │ └── tests/ # TestNG test scenarios
│ │ └─XML/ # TestNG configuration files
│ │
│ └── utility/ # Helper classes (MyFunc, etc.)
│
├── tests_gif/ # Test GIFs
│
└── README.md # Project documentation
- src/eJunkie/base/: Contains the
BaseDriverclass and core structure. - src/eJunkie/elements/: Contains Page Object classes (POM) for each page.
- src/eJunkie/methods/: Contains methods for user actions.
- src/eJunkie/tests/: Contains TestNG test scenarios.
- src/eJunkie/tests/XML/: Contains TestNG configuration files.
- src/eJunkie/utility/: Contains helper classes like
MyFunc, etc. - tests_gif/: Contains GIFs demonstrating test scenarios.
- README.md: Contains project documentation.
📌 As a customer, I want to add an eBook to the basket and try applying an invalid promo code, so I can check whether the system correctly displays the "Invalid promo code" warning.
✅ Expected: "Invalid promo code" warning message is displayed after clicking “Apply.”
✅ Actual: After adding the eBook to the basket and entering an invalid promo code, the system displayed the warning message "Invalid promo code" upon clicking “Apply.”
📌 As a customer, I want to attempt payment without entering required fields like email or billing name, so I can confirm that the form validations are triggered.
✅ Expected: "Invalid email" and "Invalid billing name" error messages are displayed.
✅ Actual: When the required fields like email and billing name were left empty, the system triggered the form validations and displayed the error messages "Invalid email" and "Invalid billing name."
📌 As a customer, I want to enter a fake card number during payment so I can verify that the system blocks invalid card details.
✅ Expected: "Your card number is invalid" warning appears.
✅ Actual: When a fake card number was entered, the system correctly blocked the payment and displayed the warning message "Your card number is invalid."
📌 As a customer, I want to complete the payment with valid card details so I can receive confirmation of a successful purchase.
✅ Expected: "Your order has been confirmed. Thank you!" is displayed.
✅ Actual: The payment was completed successfully with valid card details, and the message "Your order has been confirmed. Thank you!" was displayed.
📌 As a customer, I want to be able to download the eBook immediately after a successful purchase.
✅ Expected: File download starts and matches the purchased content.
✅ Actual: The eBook download started immediately after the successful purchase and matched the purchased content.
📌 As a customer, I want to send a message through the contact form to get support, and if CAPTCHA is not verified, I should be warned.
✅ Expected: "Recaptcha did not match" error message appears.
✅ Actual: "Recaptcha did not match" error message appeared.
📌 As a customer, I want to navigate from the demo site to the official e-junkie homepage to verify the redirection works correctly.
✅ Expected: Final URL matches e-junkie.com.
✅ Actual: Final URL matched e-junkie.com.
📌 As a customer, I want to play the 'How it works' video and ensure it starts, plays for 10 seconds, and closes properly.
✅ Expected: Video plays and closes after 10 seconds.
✅ Actual: The video started playing successfully, continued for 10 seconds, and closed as expected without any issues.
| Test Scenario | Status | Priority |
|---|---|---|
| Add eBook to cart & invalid promo code | ✅ Passed | Medium |
| Payment attempt with missing information | ✅ Passed | High |
| Invalid card number payment attempt | ✅ Passed | High |
| Successful payment with valid card | ✅ Passed | High |
| Can user download the eBook | ✅ Passed | High |
| Submit contact form | ✅ Passed | Medium |
| Access main e-junkie page | ✅ Passed | Low |
| Access 'How it works' video | ✅ Passed | Low |
| Tool / Technology | Description |
|---|---|
| Java | Programming language |
| Selenium WebDriver | Web automation framework |
| TestNG | Testing framework |
| TestNG XML | Manages test configurations and groups |
| Maven | Dependency management and compilation operations in the project |
| Page Object Model | Reusable and maintainable test design |
| Git / GitHub | Version control |
To ensure the project runs correctly, the following libraries must be added to the project:
- Selenium
- TestNG
- Apache Commons IO
- SLF4J NOP
| Name | Role | User Story |
|---|---|---|
| Yiğit Çam | Project Lead - QA Automation Eng. | US_301 |
| Zafer Ataklı | QA Automation Engineer | US_306, US_307 |
| Rıfat Batır | QA Automation Engineer | US_304,US_305 |
| Nuri Öztürk | QA Automation Engineer | US_308 |
| Azim Korkmaz | QA Automation Engineer | US_303 |
| Mert Can Özdemir | QA Automation Engineer | US_302 |
Note: This is a collaborative QA training project.
📂 E-Junkie TestNG Automation Repository
This project is licensed under the MIT License.