DEV Community

Saarathi Academy for Saarathi Academy

Posted on Edited on Originally published at linkedin.com

What beginners miss in quality assurance training in Kathmandu

Most beginners in quality assurance training in Kathmandu test what the screen shows and stop there. The bugs that matter hide at the edges of a form, in the API behind the screen, and in the database.

Check those three places first, and learn to write a bug report a developer can reproduce. Pick up an automation tool after that. Below are five mistakes we see beginners make, and what to do instead.

Is quality assurance training in Kathmandu about software or factories?

Search for this kind of course and you will also find courses on factory rules for medicines (GMP) and ISO quality standards. Those prepare people for pharmaceutical and manufacturing work.

If you want software QA training, the kind that tests apps and websites, look for software testing words in the syllabus. Test cases, bug reports, Jira, API testing and automation are good signs.

Mistake 1: Testing only the happy path

The happy path is the normal way a user fills a form. The data is right, they tap once, and the network is good. It usually works, because the developer already tried it.

Test the edges instead. Take a mobile number field. Nepal mobile numbers have 10 digits, so try 9, 10 and 11 digits. Then try letters, spaces and an empty box. This is called boundary value analysis. It is one of the first test design methods testers learn, and it is quick to do.

Many apps in Nepal move money, so add payment edges too. Tap Pay twice on a slow connection. Wait for an OTP to expire, then enter it. Close the app halfway through a payment. One tap must mean one debit, and a failed payment must not take money.

Mistake 2: Writing "it does not work" bug reports

Mozilla's bug writing guidelines say a developer who can reproduce a bug is likely to fix it. That is why they call the steps to reproduce the most important part of a report. They also warn against vague lines like "It doesn't work".

A report a developer can act on has these parts:

  • A title of about 10 words that names the problem, not your idea for a fix.
  • Numbered steps from a clean start, so anyone can repeat them.
  • What you expected and what actually happened, written apart.
  • The browser, device and app build you used.

Write one bug per report. When two problems share one report, one of them is easy to forget.

Mistake 3: Trusting the "Saved" message

A green "Saved" message only proves that the screen showed a green message. The request behind it may have failed.

Open Chrome DevTools with Ctrl+Shift+J (Command+Option+J on a Mac), click the Network tab, and do the action again. Click the request, then look at its status and its Response tab. A success message on top of a 500 server error is a real bug, and a good one to report.

Then check the data itself. If a form says it saved a user, a short SQL query on the test database should find that user.

Job posts in Kathmandu ask for this too. For example, one QA engineer post on merojob from August 2025 lists backend testing with API and database validation, and names Postman. Those sit next to the usual checks of the user interface and different browsers.

Mistake 4: Fixing flaky tests with a fixed wait

When beginners start automation, a test fails now and then. So they add a fixed wait of three seconds. The test passes on their laptop, then fails again on the slower server that runs the tests on every code change.

Modern tools already wait for you. Before Playwright clicks a button, it checks that the button is visible, stable, enabled and able to receive the click. Only then does it click.

If a test is still flaky, find out why it failed instead of waiting longer. Playwright's trace viewer replays the failed run step by step, so you can see what the page was doing at that moment. Our post on QA automation training in Nepal for QA engineers covers what changes when a manual tester starts to automate.

Mistake 5: Pasting AI-written tests without reading them

AI tools now write test code in seconds. The risk is a test that passes whether the feature works or not, because it checks nothing that matters.

Read every AI-written test with one question in mind. Would this test fail if the feature broke? If you cannot answer yes, fix the check or delete the test. The commit goes out under your name, so the test is yours.

How does Saarathi Academy order its quality assurance training in Kathmandu?

Saarathi Academy in Old Baneshwor, Kathmandu, runs its software quality assurance training in Kathmandu in this order on purpose. Weeks 1 to 3 are manual testing. They cover test design methods like boundary value analysis, bug reports in Jira, and payment scenarios such as OTP expiry and double taps.

Week 4 adds API testing with Postman and SQL for checking the database. Weeks 5 to 7 automate tests with Playwright. From Week 6, an AI tool drafts tests and you review every line.

Classes run in person and online. There are up to 10 students in the classroom per batch, and a few online. Mentors still do the job they teach. The course ends with a certification exam taken online at home.

What can you try tonight?

Pick a signup or contact form on any site you use. Type only what a normal user might mistype, never attacks, since you do not own that site. Keep the DevTools Network tab open while you try three boundary values on one field.

Then write up the strangest result as a bug report, using Mozilla's guidelines as your checklist. If that hour felt interesting rather than boring, QA may suit you.

The week-by-week plan is public on the course page and in the syllabus, so you can read every week before you pay anyone.

Common questions

How do I start a QA career in Nepal?

Start a QA career with manual testing: test design, test cases and bug reports a developer can reproduce. Then learn API testing with Postman and simple SQL. Add one automation tool after that, and read real job posts to see which tools they name.

Manual testing vs automation testing: what is the difference?

In manual testing, a person uses the software and checks it against a plan. In automation testing, code runs those same checks again and again. Both start from the same question: what could go wrong, and how would you show it?

Can I learn software testing in Nepal without coding?

Yes, you can start software testing in Nepal without coding, because the first weeks are manual testing. At Saarathi Academy, JavaScript self-study starts in Week 2, 30 minutes a day. Week 5 opens with a live JavaScript clinic before Playwright.

What does a junior QA engineer check besides the screen?

A junior QA engineer also checks the API behind the screen and the data in the database. Postman sends requests straight to the API, and a short SQL query shows whether the data really saved. Job posts in Kathmandu name both, next to the usual browser checks.

Top comments (0)