04 · Testing Basics
What is Software Testing?
Testing is quality control for software. It confirms the product does what it should and surfaces what it
gets wrong, early enough to fix cheaply. Mohali has a large study-abroad and immigration consultancy sector,
so take an application tracker used by one of those firms. A tester makes sure an IELTS band below the
university's minimum triggers a warning, that uploading a passport larger than the size limit shows a clear
error, that the visa-file status cannot jump from 'documents pending' straight to 'approved', that a
counsellor sees only their own students and that a parent's login shows progress but cannot edit the file.
Behind those checks is a repeatable process. Find the high-risk areas. Write cases with steps, data and
expected outcomes. Run them, manually or as scripts. When something fails, log it with evidence, then retest
once it is fixed. That process runs at four levels, from a single function up to user acceptance, and it
reaches beyond features to load, security, accessibility and behaviour on different devices. On Agile teams,
it runs sprint by sprint, with automated checks firing on each merge. For a consultancy whose students are
applying to universities on deadlines, a missed bug in the tracker is not a small thing: it can mean a missed
intake.
Types of Software Testing You Will Practise
Each testing type below is linked to the module where you practise it.
| Type |
What it checks |
Covered in |
| Functional testing |
Features behave as the requirement states |
Modules 1–2 |
| Smoke & sanity testing |
A new build is stable enough for deeper testing |
Module 2 |
| Regression testing |
Recent changes have not broken existing features |
Modules 2, 6, 7 |
| Cross-browser testing |
Consistent behaviour across Chrome, Firefox, Edge and WebKit |
Modules 6–7 |
| Database testing |
Stored and returned data is correct |
Module 4 |
| API & integration testing |
Services exchange data correctly |
Modules 8–9 |
| Exploratory testing |
Unexpected behaviour scripts would miss |
Module 2 and capstone |
What Does a Software Tester (QA Engineer) Do?
On a Mohali QA desk, the week usually runs like this: groom stories with the devs, write cases and test data,
smoke-test each new build, log Jira issues with evidence and exact steps, verify the fixes. Automation
engineers additionally keep the Selenium or Playwright repo in shape, add API coverage and debug red
pipelines. Because many Mohali teams serve overseas clients, testers also join client calls, explain defects
in plain English and sometimes test overnight against a US or Canadian release window. QA's input decides
whether a build ships.
Manual Testing vs Automation Testing vs API Testing
Tricity recruiters now ask for a bit of all three. Quick comparison:
| Aspect |
Manual Testing |
Automation Testing |
API Testing |
| What it checks |
Features as a user sees them |
Repeated UI and regression checks via scripts |
Business logic and data exchange behind the UI |
| Main tools |
Jira, test case sheets, browser dev tools |
Selenium, Playwright, PyTest/TestNG |
Postman, REST APIs |
| Coding needed |
None |
Moderate (Python, Java or JavaScript/TypeScript) |
Low to moderate |
| Best for |
Exploratory, usability, new features |
Regression, cross-browser, CI/CD runs |
Fast, stable checks of services |
| Indicative salary (India) |
₹3–6 LPA (Manual QA Engineer) |
₹4–8 LPA (Automation Test Engineer) |
₹5–10 LPA (API Test Engineer) |
Salary ranges are indicative India ranges and are not guaranteed placement outcomes.
Course Overview — Who Should Join?
The course is six months long and split into thirteen modules, adding up to 165+ hours across 100+ live
sessions. Start with testing basics, manual design, Agile workflow and SQL. Then code in Python or Java and
drive real browsers with Selenium and Playwright. Then APIs, first in Postman, then in code. Then two modules
of Gen AI for QA, and a framework module wired into CI/CD. A capstone of 20 hours brings it all together.
- Students and pass-outs from Mohali, Kharar and Landran colleges and the wider Chandigarh University and
Punjabi University belt.
- Manual testers in IT City or Phase 8 firms looking to add automation and API testing.
- Staff from Mohali's BPO, immigration, banking and retail sectors who want a technical career.
- Learners in Ropar, Patiala, Fatehgarh Sahib or Ludhiana who prefer live classes from home.
- Developers wanting proper training in test design, frameworks and CI.
By graduation, you will be able to:
- Translate a user story into scenarios, cases and data sets that hit the edges and the invalid paths.
- Validate database state with SQL and write bug reports that developers can act on immediately.
- Build Selenium or Playwright suites and run them across browsers.
- Exercise APIs in Postman and turn those checks into automated, data-driven tests.
- Use AI assistants responsibly and execute suites via Jenkins with Allure dashboards.
Eligibility: any graduate or final-year student from any stream; no coding background required. For
lab days, use a laptop with at least 8 GB RAM and Wi-Fi or mobile data that holds steady.
4.7/5
4.7/5
5/5
4/5
5/5
5/5
_2.webp)
_3.webp)
Selenium
Playwright
Python
Java
JavaScript /
TypeScript
Postman
REST APIs
SQL
PyTest /
TestNG
Git
GitHub
Jenkins
Jira
ChatGPT
GitHub Copilot
Allure Reports
