Syllabus
Software Testing Course Syllabus in Amritsar
The 165 hours are organised into thirteen modules that follow a tester's widening
responsibilities: hand-testing, database checks, page scripting, endpoint testing, AI support and
finally Jenkins. A lab closes every module, and Module 13 gives you the whole result portal to own.
M1 · Fundamentals & SDLC/STLC10h
M2 · Manual Testing & Bug Reporting12h
M3 · Agile, Scrum & Test Mgmt8h
M4 · SQL & Database Testing10h
M5 · Python or Java15h
M6 · Selenium WebDriver15h
M7 · Playwright (JS/TS)15h
M8 · Postman & REST APIs12h
M9 · API Automation12h
M10 · GenAI for Test Cases & Data10h
M11 · AI-Assisted Automation12h
M12 · Framework, Git, CI/CD14h
M13 · Capstone Project20h
01Software Testing Fundamentals & SDLC/STLC10 Hours
Day one opens on a result-day scare. A girl in Tarn Taran sees "Fail" beside her name though she scored 32 in English; the portal compared against 33 without applying the grace mark that the rules allow, because a recent refactor dropped one condition. That incident anchors the first lessons: why software gets tested at all, the seven principles testers live by, how one dropped condition grows into a student's wrong result, the contrast between Waterfall, V-Model and Agile delivery, and the fit between STLC phases and the four test levels.
02Manual Testing, Test Cases & Bug Reporting12 Hours
The result engine is your design lab. Pass marks, grace limits and the re-evaluation window give boundaries; student categories (regular, private, compartment, open school) and subject groups form equivalence classes; grace, moderation and compartment rules fill a decision table; and a result moving from processed to published, re-evaluation requested, revised or final becomes a state chart. Then comes free exploration, smoke and sanity passes, and regression loops, with each bug tagged by severity and priority. Tool: Jira
03Agile, Scrum & Test Management8 Hours
Scrum on a board project: sprint planning, daily stand-ups, a review where examination officials see the demo, and a retrospective, stories closed only when their criteria pass. The portal's Jira project is yours to set up, columns, transitions, queries and a summary dashboard included, and the plan ranks pass-fail logic ahead of design polish. Tool: Jira
04SQL & Database Testing10 Hours
SQL over students, subjects, marks, results and revaluation_requests. Primary and foreign keys first, then WHERE clauses, ordering, GROUP BY with sums, joins and nested selects, applied either to fabricate believable result data or to prove that every revised mark also changed the published total. Tool: SQL
05Programming Fundamentals with Python or Java15 Hours
Programming in Python or Java with no prior knowledge assumed: types, decisions, loops, functions, classes, inheritance and exception handling. You finish with a loader that reads student and marks data from CSV, JSON or Excel so one test can recheck an entire district. Tools: Python, Java
06Selenium WebDriver & Automation Fundamentals15 Hours
Module 6 turns Selenium WebDriver on the examination officer's console. You target fields through IDs, CSS and XPath, replace sleeps with explicit waits, handle pop-ups, frames and child windows, pick districts and schools from drop-downs, read long result grids and package everything as PyTest or TestNG suites for cross-browser runs. Tools: Selenium, PyTest/TestNG
07Playwright Automation with JavaScript/TypeScript15 Hours
Module 7 opens with just enough TypeScript and moves to Playwright: role and label locators, assertions that retry, fixtures, a login stored once, a re-evaluation fee payment forced to fail, uploads of answer-sheet copies, parallel execution, and trace files that show exactly where a run went wrong. Tools: Playwright, JS/TS
08API Testing with Postman & REST APIs12 Hours
Under the console are REST services. The vocabulary comes first, request verbs, routes, headers, response codes and JSON, and then Postman collections with environment variables, token access and schema assertions. Tools: Postman, REST APIs
09API Automation & Integration Testing12 Hours
Postman requests become code: assertions on every response, a roll number carried through result and re-evaluation calls, automatic token refresh and payloads loaded from data files. Finally one re-evaluation request travels end to end, endpoint to fake fee service to database, and that test joins the browser suite on a schedule. Tools: REST APIs, PyTest/TestNG
10GenAI for Test Case Generation & Test Data10 Hours
A fresh moderation rule arrives from the board. Gen AI is asked to brainstorm situations, rare edge cases and fictional candidates; you then audit what it produced, flagging misses and mistakes, and learn why students' names, roll numbers and marks must never be pasted into a public AI tool. Tool: ChatGPT
11AI-Assisted Automation, Debugging & Test Maintenance12 Hours
ChatGPT and GitHub Copilot work as your pair: they draft test methods, propose cleaner code, explain inherited functions, decode stack traces and patch locators that break at random; you execute and understand each line before it reaches Git. Tools: GitHub Copilot, ChatGPT
12Framework Design, Git, CI/CD & Test Reporting14 Hours
Module 12 refactors your scripts into an organised framework, with page classes, separate data files, reviewed Git merges, Jenkins builds on each commit and Allure summaries that the board's IT cell can read. Tools: Git, GitHub, Jenkins, Allure Reports
13End-to-End Testing Project & Capstone20 Hours
You are responsible for the result portal's quality: you draft its test plan, execute every case, script the student screens, the officer console and the services, and make each GitHub push start a Jenkins build. The final sessions are about getting hired: a tighter résumé and LinkedIn, a short demo of your repositories rehearsed, and mock panels. Tools: All tools
Total: 13 Modules · 165 Hours · 15+ Tools & Technologies. Curriculum reviewed by Mr. Satyendra Bind, corporate trainer in manual, API and Selenium-Java automation testing.
4.7/5
4.7/5
5/5
5/5
_3.webp)
