QA Insights with Vikas

In this post, I’ll walk you through the complete workflow of my Cucumber BDD Framework project, which I developed to automate test scenarios for the website Automation Practice . You can explore the full project here: GitHub Repository . 1. Project Overview This project is a hybrid automation framework based on Cucumber BDD using Java, Selenium WebDriver, and Maven . It supports Page Object Model (POM) , and integrates with Jenkins CI/CD and GitHub for version control. 2. Folder Structure 📋 Folder Summary Table Folder/File Purpose .vscode/ IDE-specific settings and preferences. .mvn/ Maven runtime configurations. src/main/java/com Core reusable framework classes. factory/ WebDriver setup and initialization. pages/ Page Object Model (POM) design classes. utilities/ Helper functions and utilities. src/test/java/ Step definitions, hooks, and test runners. resources/com Feature files and ...

As a QA Engineer, knowing Git (version control) and GitHub (remote repository hosting) is not optional anymore. Modern QA workflows – whether manual or automation – rely on Git for: Collaborating with developers & other testers Maintaining test automation frameworks Tracking changes in test scripts, data, and documentation Rolling back safely when bugs are introduced Tip for QAs: Treat your automation scripts, test cases, and configuration files just like code. Version control ensures no work is lost and every change is traceable. Git Basics Every QA Must Know Command What it does / Example git clone <repo-url> Download a remote repo locally. Example: git clone https://github.com/org/repo.git git status Check which files are staged, unstaged, or untracked. git add . Stage all changes for commit. Use carefully – better to stage specific files durin...