Software Testing Basics: Principles, Models and Techniques

Software testing basics are the foundational principles, lifecycle models and test design techniques that QA professionals use to find defects before software reaches users. The discipline covers the seven ISTQB principles, models like the V-model and Agile testing, and black-box techniques such as equivalence partitioning, boundary value analysis and decision tables.

• Key Takeaway 1: There are exactly seven universally accepted principles of software testing, and interviewers test you on all of them.
• Key Takeaway 2: The V-model and Agile testing model are the two lifecycle models you will encounter most in Indian IT firms.
• Key Takeaway 3: RTM (Requirements Traceability Matrix) links every test case back to a business requirement, so nothing gets missed.
• Key Takeaway 4: Decision tables and domain testing are black-box techniques that help you design test cases without reading a single line of code.
• Key Takeaway 5: Manual testing skills are still the hiring baseline at most Indian product and service companies, especially for freshers.

The Seven Principles of Software Testing

The International Software Testing Qualifications Board (ISTQB) defines seven principles that every QA professional should know cold. These are not abstract theory. They shape how test plans are written, how much testing is enough, and how defect reports are justified to developers and project managers. Mastering these testing basics is the first step toward clearing any QA screening round.

Principles 1 to 4: The Foundation of Testing Basics

1. Testing shows the presence of defects, not their absence. You can run 10,000 test cases and still not prove the software is bug-free. Testing reduces risk; it does not eliminate it.

2. Exhaustive testing is impossible. You cannot test every input, every path, every combination. Risk-based prioritisation decides what gets tested first. This is why test case design is central to testing basics.

3. Early testing saves money. The IBM Systems Sciences Institute documented that fixing a defect found in production can cost up to 100 times more than catching it during requirements review. The earlier testing starts, the cheaper the fix.

4. Defect clustering. A small number of modules typically contain most of the bugs. The Pareto principle applies here: roughly 80% of defects tend to cluster in 20% of the codebase. Experienced testers aim their effort at high-risk areas first.

Principles 5 to 7: The Testing Basics Freshers Usually Miss

5. The pesticide paradox. If you run the same test cases repeatedly, they stop finding new bugs. Test suites need to be reviewed and updated continuously. This is a common trap in teams that rely on static regression packs.

6. Testing is context-dependent. How you test a banking app is completely different from how you test a gaming app. Safety-critical systems need far more rigorous testing than a marketing landing page.

7. Absence-of-errors fallacy. A system can pass every test and still be useless if it does not meet actual user needs. Verification (did we build it right?) and validation (did we build the right thing?) are both necessary parts of any testing basics checklist.

Software Testing Models and the Defect Life Cycle

A testing model describes how testing activities fit into the software development lifecycle. Choosing the right model affects when testing starts, how much it costs, and how quickly defects get fixed. According to the NASSCOM 2023 IT Workforce and Skills Report, QA roles account for roughly 15% of all active IT job postings in India, and most of those job descriptions mention at least one formal testing model as a requirement.

The V-Model

The V-model pairs each development phase with a corresponding testing phase. Requirements analysis pairs with acceptance testing, system design pairs with system testing, and so on. Testing is planned early, which directly supports principle three of the testing basics framework above.

It is the model you will see most often in BFSI (banking, financial services and insurance) projects in India because the structured approach suits regulated environments. The downside is rigidity. If requirements change mid-project, the whole left side of the V needs revisiting.

Agile Testing Model

In Agile, testing happens inside every sprint rather than at the end of the project. Testers collaborate with developers and product owners from day one. This shortens the feedback loop and reduces defect leakage into production significantly.

The 2023 State of Agile Report published by Digital.ai found that 71% of organisations globally use Agile methods, and Indian IT services firms like Infosys, Wipro and TCS have all formalised Agile QA practices internally. If you are joining a product team, expect Agile testing to be the default model you encounter.

The Defect Life Cycle

Every bug follows a lifecycle: New, Assigned, Open, Fixed, Retest, Verified, Closed. Some bugs get Rejected (not a defect), Deferred (fix later) or Duplicate (already logged). Knowing this flow is non-negotiable for any manual testing interview. Tools like JIRA, Bugzilla and Azure DevOps manage this workflow in most Indian IT shops.

Comparison of Common Testing Models

Testing Techniques: Black-Box, White-Box and RTM in Testing

Testing techniques tell you how to design test cases. The two main families are black-box (no code knowledge needed) and white-box (you look inside the code). Most fresher QA roles start with black-box techniques, which is why they dominate manual testing interview questions and form the core of software testing basics training.

Black-Box Techniques Every Fresher Must Know

Equivalence Partitioning divides input data into valid and invalid partitions. You test one value from each partition instead of every possible value. If a field accepts ages 18 to 60, you test one value below 18, one between 18 and 60, and one above 60.

Boundary Value Analysis targets the edges of those partitions, because defects cluster at boundaries. For the same field, you would test 17, 18, 19, 59, 60 and 61.

Domain testing extends this by considering multiple input variables together. It is especially useful for financial applications where combinations of account type, transaction amount and currency can produce unexpected behaviour.

Decision tables are one of the most powerful black-box tools in the testing basics toolkit. A decision table lists all possible combinations of conditions (inputs) and the corresponding actions (outputs). It is particularly useful when business rules are complex, like loan eligibility systems at banks. Each column in the table represents one test case, making it easy to achieve complete condition coverage without missing a combination.

What RTM in Testing Actually Does

An RTM, or Requirements Traceability Matrix, is a document that maps every requirement to one or more test cases. It runs both ways: forward tracing (requirement to test case) confirms coverage, and backward tracing (test case to requirement) confirms there are no orphan tests covering things nobody asked for.

In practice, an RTM is a spreadsheet with columns for Requirement ID, Requirement Description, Test Case ID and Test Status. Project managers use it to report test coverage to clients. Testers use it to identify gaps. The ISTQB Foundation Level syllabus explicitly covers RTM as a core QA artefact, and it comes up in almost every functional testing interview at companies like Cognizant, HCL and Capgemini.

White-Box Techniques

White-box testing requires code access. Statement coverage, branch coverage and path coverage are the three main techniques. A developer or a technically strong tester checks that every line, every conditional branch and every execution path has been exercised at least once.

This is where debugging intersects with testing. Debugging is the process of identifying the root cause of a defect once testing has found it. Testing finds the symptom; debugging finds the disease. They are related but distinct activities, and mixing them up in an interview is a red flag for interviewers.

If you are building skills in this area, the top skills every college student should learn before graduation article on 3.0 University gives a broader picture of where testing basics fit alongside programming and data skills. If you are exploring which certifications pay off fastest, the guide to top online courses for high-salary jobs is worth reading alongside this one.

Software Testing Basics: Manual Testing Interview Prep for Freshers

Freshers applying for QA roles at Indian IT companies face a fairly predictable set of screening questions. The ISTQB Foundation Level certification (offered by GASQ and other accredited bodies in India) is the most recognised entry-level credential, and its syllabus covers all the testing basics in this article. According to the ISTQB 2023 Annual Report, India ranks among the top five countries globally for Foundation Level exam registrations, reflecting the scale of QA hiring in the Indian market.

What Interviewers Actually Ask Freshers

Expect questions on the seven principles, the defect life cycle, test case writing (with a test case description for a login page or ATM), difference between smoke and sanity testing, and RTM structure. You will almost certainly be asked to write a decision table for a simple business rule on the spot.

Practice writing test cases for everyday scenarios: a search bar, a registration form, a payment gateway. If you can explain why you chose boundary values or how you would structure an RTM for five requirements, you are ahead of most other freshers in the room.

For broader career direction, 3.0 University’s guide on how to choose the right career path after graduation helps you decide whether QA, development or another IT track suits your strengths. If you are comparing QA against other options, the best career options in 2026 for students and professionals breakdown is a practical starting point.

Manual vs Automated Testing: Know the Boundary

Manual testing means a human executes test cases step by step without scripting. It is essential for exploratory testing, usability checks and one-off scenarios. Automated testing uses tools like Selenium, Cypress or Appium to run scripts repeatedly, making it cost-effective for regression suites.

Neither replaces the other. Most QA teams in India use manual testing for new features and automation for stable, frequently-run regression packs. As a fresher, manual testing basics get you hired; automation skills get you promoted. Free resources on platforms listed in 3.0 University’s guide to free online learning platforms for students can help you start learning Selenium basics without spending a rupee.

Your Action Plan This Week

1. Write out the seven testing principles from memory without looking at notes. If you cannot, review this article and try again tomorrow.
2. Draw a V-model diagram and label each phase with its corresponding test type.
3. Build a simple RTM for a five-requirement login module. Use a spreadsheet with columns: Req ID, Requirement, Test Case ID, Test Case Description, Status.
4. Write a decision table for a discount rule: customers over 60 or with a loyalty card get 20% off; all others pay full price.
5. Register for the ISTQB Foundation Level exam through an accredited Indian provider and set a target exam date within 60 days.

If you are looking at entry-level jobs for teens and graduates, QA is one of the most accessible starting points in the Indian market, with low barriers to entry and a clear progression path to senior tester, test lead and QA manager roles. The 3.0 University course catalogue also covers technical domains that complement a QA career, from cybersecurity to AI, if you want to specialise down the line.

3.0 University offers online certification programmes in Cybersecurity, Ethical Hacking, AI, Blockchain and Web3 designed specifically for students, working professionals and career switchers in India. If you want practical, industry-ready skills that go beyond theory, exploring those programmes is a logical next move after you have nailed these testing basics.

Frequently Asked Questions

What are the seven principles of software testing?

The ISTQB defines them as: testing shows presence of defects, exhaustive testing is impossible, early testing saves cost, defect clustering, the pesticide paradox, testing is context-dependent, and the absence-of-errors fallacy. All seven apply to both manual and automated testing contexts and are standard knowledge for any QA screening interview in India.

What is an RTM in testing?

An RTM (Requirements Traceability Matrix) is a document that maps each business requirement to one or more test cases. It helps QA teams confirm full test coverage, identify gaps, and report progress to stakeholders. Forward tracing goes from requirement to test case; backward tracing goes from test case back to requirement to eliminate orphan tests.

What is the difference between manual and automated testing?

Manual testing involves a human tester executing test cases step by step without scripts. Automated testing uses tools like Selenium or Appium to run pre-written scripts. Manual testing suits exploratory, usability and ad-hoc scenarios. Automation suits stable regression suites run repeatedly. Most Indian QA teams use both, with freshers starting on the manual side before progressing to automation tools.

What is a decision table in software engineering?

A decision table maps every combination of input conditions to the corresponding expected output or action. Each column represents one test case. It is a black-box technique used when business rules are complex, like insurance eligibility or loan approval logic. Decision tables guarantee complete condition coverage and make it easy to spot missing test scenarios.

What testing questions are asked to freshers?

Common fresher QA interview questions include: explain the defect life cycle, write test cases for a login page, what is the difference between smoke and sanity testing, what is an RTM, explain boundary value analysis, and draw a V-model. Interviewers at companies like Infosys, Wipro and Capgemini often ask candidates to write a decision table on the spot.

What are software testing basics for beginners?

Software testing basics for beginners include understanding the seven ISTQB principles, the defect life cycle, black-box techniques like equivalence partitioning and boundary value analysis, the RTM document, and the difference between the V-model and Agile testing. These fundamentals form the complete foundation for any entry-level QA role in India.

Last updated: June 2025. Reviewed by the 3University editorial team.