How dhanusheswaranm/python_selenium works
Project type and purpose
• This repo is a monorepo of multiple Python‐based Selenium test automation frameworks, each organized around the Page Object Model (POM) pattern.
• Its primary purpose is end-to-end UI testing of web applications: tests drive a browser via Selenium, use page classes to abstract element locators and actions, read data/config from Excel or INI files, and emit JSON/XML/HTML reports.
File structure
• Top‐level folders correspond to individual sample frameworks (DemoPythonSelenium, POM, PageObjectModel, Task, Task2, datadriframe, fixture, pagefactory, pytest).
• Within each:
• Pages or Pages/HomePage.py, SearchPage.py → Page Object layer
• Tests or Tests/**test_*.py, conftest.py** → Test layer (pytest fixtures, test cases)
• Utility or Utilities/read_config.py, excelReader.py → Helpers (config reader, data provider)
• config.ini files → External configuration
• ExcelFiles/*.xlsx → Test data
• Reports or XMLReport.xml / report.html → Test results
• hooksfunctionallevel.py / consolelogger.py → Logging and hooks
• There are also common elements: .vscode settings, a root README.md, and various __pycache__.
Detail
• Config files and data sources explicitly.
• Don’t omit the pytest fixture layer – it’s where browser setup and teardown happen.
• Both synchronous (test → page) and asynchronous or plugin-based (pytest hooks → logger) flows.