Software Testing · Lesson 1 of 8

What software testing is

Why we test, verification vs validation, and where testing fits in the SDLC and STLC.

Software testing checks that software does what it should, and finds problems before users do. A tester thinks like a user, a critic and a detective at the same time.

Verification vs validation

  • Verification — "Are we building the product right?" Reviews of requirements, designs and code against specifications.
  • Validation — "Are we building the right product?" Running the software to confirm it meets real user needs.

Where testing fits

The SDLC (software development life cycle) covers requirements, design, development, testing, deployment and maintenance. Testing has its own life cycle, the STLC:

  1. Requirement analysis — what needs testing, and what is unclear?
  2. Test planning — scope, approach, tools, schedule, risks.
  3. Test case design — write cases and prepare test data.
  4. Environment setup — where tests will run.
  5. Test execution — run cases, log bugs, retest fixes.
  6. Test closure — report results, lessons learned.

Finding a defect in requirements costs far less than finding it after release, which is why good teams involve QA early ("shift left").

Example

Practise on any app you use
Requirement: "Users can reset their password by email."

Questions a tester asks before writing a single test:
  • How long is the reset link valid?
  • What happens if the email isn't registered?
  • Can an old link be used after a new one is sent?
  • What are the password rules (length, characters)?
  • Is there a limit on reset requests per hour?

What to notice

• Testing starts at the requirement, not after coding.
• Every unclear point becomes either a clarified requirement or a test case — this is "shift left" in practice.
• Asking good questions is a core QA interview skill.

Apps, IDs and data are fictional examples written for practice.

Key points

  • Testing finds problems before users do.
  • Verification = built right; validation = right product.
  • STLC: analyse → plan → design → set up → execute → close.
  • Earlier defects are cheaper to fix.

Quick check

Which question describes validation?

Practice task

Pick a feature in an app you use daily (for example UPI payment). Write ten questions you'd ask about its requirements before testing it.

Interview corner

What is the difference between QA and QC?

QA (quality assurance) is process-focused — preventing defects through good practices. QC (quality control) is product-focused — finding defects by testing the actual product.

Why is testing needed if developers write good code?

Everyone makes assumptions; testers bring an independent view, test unusual paths and real-user behaviour, and catch integration issues no single developer sees.

Original lesson written by the InfoparkDaily team · © 2026 InfoparkDaily · Free to learn — no paid course or subscription.