MODULE_01
QA and software testing
Test plans written before the first commit, not after the first bug report.
- Cypress
- Postman
- Selenium
- Regression
- CI gates
- Contract QA
What this actually covers
Manual and exploratory testing, automated regression suites, API contract testing, and release gates that fail loudly rather than quietly.
The tooling is Cypress for browser flows, Postman and Newman for API suites, and Selenium where a legacy stack requires it. The tool matters far less than whether anybody runs it on every push, which is the part that usually goes missing.
Why it sits before the build, not after
A test plan written after the feature is a description of what was built. A test plan written before it is a specification, and the difference shows up as the number of things that get argued about at release.
The practical version: acceptance criteria first, then the suite that proves them, then the implementation. It is slower for a week and faster for a year.
What a regression suite is for
Not for finding new bugs. For proving that the thing that worked last month still works, on every deploy, without a person remembering to check.
The suites we build are the ones that run in CI and block a merge. A suite that lives on somebody's laptop and gets run before big releases is documentation, not a gate.
Hiring a QA engineer, or hiring the practice
People who come here looking to hire a QA engineer in Nepal are usually solving one of two problems. Either there is no test discipline and somebody has to build one from nothing, or releases keep breaking and nobody can say why. They need different work in the first month and it is worth being clear which one you have before anybody quotes you.
QA testing services for startups almost always means the first. A pre-Series-A team does not need a QA department; it needs the three things that stop a demo breaking — a regression suite on the paths that take money, a release checklist somebody actually follows, and a bug that gets reproduced before it gets argued about. That is a scoped engagement, not a headcount.
We work as an embedded contractor rather than an outsourced test house: in your repo, in your CI, writing suites your engineers can read and run after we leave. A test suite nobody on your team understands is a liability with a green tick on it.