Creators: Alon Belker
Date: 16/3/2023
Appendencies: Traceability Table in Google Sheets

We were 4 QA students in a college called "IITC College" in Ramat Gan, Israel.
As part of our studying we received a project to test demoblaze.com - find bugs, asking questions, test where the site could fail.
We were required to use Selenium package in order to automate the tests.
After one week of work around this project we finally finished with the project

For our surprise, after the submission we were required to turn the project into a POM model. The side effect was a division in our project and grow paths separately.

Before we started building tests we had to explore the site, as no one was familiar with site before. We started with exploratory tests, trying to figure out the content and purpose of the site.
Afterwards we started to think about the structure of the project files.
We decided to go with POM (Page Object Model) model and start build the structure.
First thing we wanted was to import our needed packages and an easy way to pull those at once. We created a file called "utils.py" which includes the package imports we need for most of the project.

first few lines of utils.py: 

import selenium
import requests

from selenium import webdriver as WebDriver
from selenium.webdriver.common.by import By
from selenium.webdriver.common.keys import Keys

We needed a "tests" package to include the automatic test cases.
We also wanted a "pages" package to include functions within pages, thus, for example, we can log in easily from everywhere we need to.
After a little more time we realized we can optimize the work when using "locators". the locators file include a class called "Locator" and dictionaries of web elements we gathered to easily access them. We made locators classes per page for ease of use and better readability. In order to easily call I created a "index" file which will get the locators classes into one file.

We also had writing conventions. To further read open the "README_conventions.md"

https://demoblaze.com is a demo website for electronics e-commerce store
The site sells Phones, Laptops and Monitors

In this project we had to make tests on this site.
Meaning we had to assess how valid is the website to operate successfully

The short answer is: NO
The long answer has to dig in the suggestive requirements:

• Homepage - The main page
• Contact - A modal contains sending message option
• About Us - A modal contains video information on demoblaze.com
• Cart - A site contains the cart info
• Log In - A modal which allows users to log in
• Sign Up - A modal which creates users
• Product - A page dedicated for viewing product

You are welcomed to dig in our project and look for the tests and bugs

• "src" folder stands for sources and contains files that could utilize the automated tests
• "Pages" folder contains functions relevant for certain pages
• "Tests" folder contains the test suites and test cases for each requirement
• "Locators" folder contains locators for different sections in the site
• utils.py is a file which takes in the imports
• run_all.cmd runs all the tests in a sequence, non-stop

in order to run the tests locally you have to download (get git) the git and create new virtual environment.

• Selenium
• unittest
• pytest

in order to run all tests you have to run the "main.py" or "run_all.cmd"