MCA 120 Software Testing Notes from Unnati Educations cover all 4 units of this GGSIPU MCA Semester 2 Core Elective in 83 pages, with 19 solved examples, 48 short-answer questions with answers and 46 long-answer questions with answer outlines. They follow the MCA syllabus for batches admitted from 2025-26 onwards.
Written by Prateek Talwar, Founder, Unnati Educations · Reviewed by Ritik Rawat, B.Tech, Senior Full Stack Developer · Checked against the MCA Scheme of Examination and Detailed Syllabus (BoS USIC&T, 28 July 2025) · Updated 14 October 2026 · Editorial policy
Scheme: MCA scheme 2025-26 (USIC&T, affiliated institutes) | Applies to: batch admitted 2025-26 onwards | Verified against: MCA Scheme of Examination and Detailed Syllabus, effective Academic Year 2025-2026
MCA 120 Software Testing at a glance: GGSIPU MCA Sem 2 credits, units and exam pattern
MCA-120 is one of ten Core Elective I options in Semester 2 of the two-year MCA scheme that GGSIPU runs at its affiliated institutes. These MCA 120 Software Testing IPU notes follow its four units in the same order.
| Code and title | MCA-120 Software Testing |
|---|---|
| Course and semester | MCA (2 years), Semester 2 |
| Category | Core Elective I (choose one of MCA-108 to MCA-126) |
| Credits and weekly hours | 4 credits · L 3, T/P 1 |
| Marks | 100: 60 end-term + 40 internal (the remainder of 100; the PDF does not print the split as a separate line). Passing: 40 out of 100 |
| End-term pattern | Compulsory Q1 (objective or short answers, whole syllabus) 12 marks, plus one of two questions from each unit at 12 marks (12 + 48 = 60 marks) |
| Applies to | Batch admitted from 2025-26 onwards |
| Units | 4 units, 10 hours each; textbook TB1 Jorgensen |
| Linked lab | MCA-168 Lab based on Core Elective I (Software Testing Lab), 1 credit |
Verify every fact in this table in the official GGSIPU MCA syllabus PDF (Semester 2 scheme on page 5, passing marks in Important Note 9 on page 8, MCA-120 on pages 57-59). The programme follows Ordinance 11 for examination rules. MCA 120 sits with the other GGSIPU MCA Semester 2 papers on one scheme page.
MCA 120 Software Testing Notes unit-wise: 19 solved examples and 94 exam questions across 4 units
The 83-page book has 69 numbered sections, and each unit ends with a quick revision sheet and a question set. The official PDF gives topic headings but no unit names, so the unit titles below use those headings. Notes for every other MCA paper sit under GGSIPU MCA notes.
MCA 120 Unit 1: Fundamentals of Testing, Testing through the SDLC and Static Testing
Pages 5 to 22, 16 sections. Unit 1 separates testing from debugging, traces error to defect to failure to incident, and gives IEEE 829 test case and test plan templates. It maps the V-Model to the four test levels with stubs, drivers and integration strategies, then covers reviews and inspection roles. No numericals; 12 short-answer and 11 long-answer questions.
| Basis | Static | Dynamic |
|---|---|---|
| Execution | Code not run | Code run |
| Finds | Defects directly | Failures, traced to defects |
| When | From requirements | After code exists |
| Techniques | Reviews, static analysis | Black-box, white-box |
Quick look: static vs dynamic testing (from page 17)
- Basis
- Execution
- Static
- Code not run
- Dynamic
- Code run
- Basis
- Finds
- Static
- Defects directly
- Dynamic
- Failures, traced to defects
- Basis
- When
- Static
- From requirements
- Dynamic
- After code exists
- Basis
- Techniques
- Static
- Reviews, static analysis
- Dynamic
- Black-box, white-box
MCA 120 Unit 2: Test Types, Functional Testing and Structural Testing
Pages 23 to 43, 16 sections, and 13 of the 19 solved examples. Black-box work runs on Jorgensen's triangle problem: four forms of equivalence classes, normal, robust and worst-case BVA, an 11-rule decision table, a state machine and a use case. One largest-of-three program then carries the flow graph, DD-paths, cyclomatic complexity, graph matrix, data flow and mutants. 12 short-answer and 11 long or numerical questions.
Quick look: cyclomatic complexity of the largest-of-three program (from page 35)
- 9 nodes, 11 edges, 1 component: V(G) = 11 − 9 + 2 = 4.
- Predicate nodes 2, 3 and 6: V(G) = 3 + 1 = 4.
- Regions: 3 enclosed + 1 outer = 4.
- So there are 4 independent paths, and 4 test cases cover every branch.
MCA 120 Unit 3: Test Management, Configuration Management, Defect Management and Regression Testing
Pages 44 to 63, 19 sections, the most of any unit. Unit 3 compares test manager and tester duties and lists the 16 IEEE 829 test plan sections. It then covers ratio-based, Wideband Delphi, Planning Poker and three-point estimation, the defect life cycle, severity vs priority, and regression selection, minimisation and prioritisation. 4 solved examples, 12 short-answer and 12 long-answer questions.
| Step | Working | Result |
|---|---|---|
| Inputs a, m, b | Given | 6, 9, 18 days |
| E = (a + 4m + b) ÷ 6 | 60 ÷ 6 | 10 days |
| SD = (b − a) ÷ 6 | 12 ÷ 6 | 2 days |
| Range | 10 ± 2 | 8 to 12 days |
Quick look: three-point (PERT) test estimate (from page 49)
- Step
- Inputs a, m, b
- Working
- Given
- Result
- 6, 9, 18 days
- Step
- E = (a + 4m + b) ÷ 6
- Working
- 60 ÷ 6
- Result
- 10 days
- Step
- SD = (b − a) ÷ 6
- Working
- 12 ÷ 6
- Result
- 2 days
- Step
- Range
- Working
- 10 ± 2
- Result
- 8 to 12 days
MCA 120 Unit 4: Test Driven Development, Object-Oriented Testing and Agile Testing
Pages 64 to 83, 18 sections. TDD gets the Red, Green, Refactor cycle, xUnit elements and pros and cons. Object-oriented testing covers encapsulation, inheritance and polymorphism problems, a capacity-3 Stack state model and MM-path integration. Agile testing covers XP, Scrum, ATDD and BDD with a Gherkin scenario, AMDD, testing quadrants, the test pyramid and exploratory sessions. 2 solved examples, 12 short-answer and 12 long-answer questions.
Quick look: the leap year method after the second TDD cycle (from page 67)
static boolean isLeap(int year) {
if (year % 400 == 0) return true;
if (year % 100 == 0) return false;
return year % 4 == 0;
}All four JUnit 5 tests pass: 2024 and 2000 give true, 2023 and 1900 give false.
Product risks vs project risks in software testing: excerpt from page 53 of the MCA 120 notes
Excerpt from page 53
11. Product risks and project risks
A product risk (also called a quality risk) is the chance that the software itself fails to meet the legitimate needs of its users and stakeholders. It is tied to quality characteristics such as correct functions, performance, security and usability. A project risk is a situation that may hurt the project's ability to reach its objectives. It is tied to how the project is managed and controlled.
| Basis | Product risk | Project risk |
|---|---|---|
| Examples | Software does not perform intended functions; wrong interest calculated; slow response; security holes; poor usability; data corruption | Late builds or environments; budget cuts and staff shortage; changing requirements; poor communication; supplier failure |
| Handled by | Testing (risk-based testing) and design reviews | Project management and contingency planning |
Product risk vs project risk (page 53)
- Basis
- Examples
- Product risk
- Software does not perform intended functions; wrong interest calculated; slow response; security holes; poor usability; data corruption
- Project risk
- Late builds or environments; budget cuts and staff shortage; changing requirements; poor communication; supplier failure
- Basis
- Handled by
- Product risk
- Testing (risk-based testing) and design reviews
- Project risk
- Project management and contingency planning
Project risk categories
- Project issues: late delivery, inaccurate estimates, late changes.
- Organisational issues: too few staff, missing skills or training, users not available.
- Political issues: testers not communicating needs, test findings not followed up, a poor attitude to testing.
- Technical issues: poor requirements, a test environment that is not ready, late data conversion, a weak development process.
- Supplier issues: a third party fails to deliver, or contract problems arise.
Four responses to a risk
Mitigation reduces the likelihood or impact, for example by testing more. Contingency is a plan B ready to use if the risk happens. Transfer moves the risk elsewhere, for example through insurance or outsourcing. Acceptance means the team knowingly lives with the residual risk.
12. Risk-based testing
Risk-based testing uses product risk information to select, prioritise and manage test activities. Testing effort is proportional to the level of risk, so high-risk areas are tested earlier and more thoroughly.
The process runs in four steps: risk identification (brainstorming, checklists, interviews), risk assessment (likelihood × impact on a risk matrix), risk mitigation (prioritising tests and choosing depth and techniques) and risk monitoring (re-assessing as testing goes on and reporting the residual risk).
How to write MCA 120 answers: BVA, cyclomatic complexity and mutation score numericals
MCA 120 mixes table-and-diagram theory answers with Unit 2 and Unit 3 numericals marked step by step.
- Structural numericals: number the code lines, draw the flow graph, list nodes and edges, compute V(G) three ways, list independent paths and give one test case per path.
- BVA: state the single fault assumption, then the formula (4n + 1 normal, 6n + 1 robust, 5ⁿ worst-case), then the table. It is 4n + 1, not 5n, because the all-nominal test is counted once (page 28).
Worked example: mutation score (page 40)
50 mutants, 40 killed, 5 equivalent.
- Mutation score = Killed ÷ (Total − Equivalent) × 100.
- 40 ÷ (50 − 5) × 100 = 40 ÷ 45 × 100 = 88.9%.
- The suite is not mutation-adequate; new tests must kill the 5 live mutants.
Practise this step format on GGSIPU MCA important questions.
MCA 120 exam corner: 48 short-answer and 46 long-answer questions by unit
| Unit | Short answers, 2.5 Marks (with answers) | Long answers, 12.5 Marks (with outlines) | Solved examples |
|---|---|---|---|
| Unit 1 | 12 | 11 | 0 |
| Unit 2 | 12 | 11 | 13 |
| Unit 3 | 12 | 12 | 4 |
| Unit 4 | 12 | 12 | 2 |
| Total | 48 | 46 | 19 |
MCA 120 notes: questions and solved examples per unit
- Unit
- Unit 1
- Short answers, 2.5 Marks (with answers)
- 12
- Long answers, 12.5 Marks (with outlines)
- 11
- Solved examples
- 0
- Unit
- Unit 2
- Short answers, 2.5 Marks (with answers)
- 12
- Long answers, 12.5 Marks (with outlines)
- 11
- Solved examples
- 13
- Unit
- Unit 3
- Short answers, 2.5 Marks (with answers)
- 12
- Long answers, 12.5 Marks (with outlines)
- 12
- Solved examples
- 4
- Unit
- Unit 4
- Short answers, 2.5 Marks (with answers)
- 12
- Long answers, 12.5 Marks (with outlines)
- 12
- Solved examples
- 2
- Unit
- Total
- Short answers, 2.5 Marks (with answers)
- 48
- Long answers, 12.5 Marks (with outlines)
- 46
- Solved examples
- 19
The MCA 120 notes answer 48 short-answer questions and outline 46 long-answer questions, plus 19 solved examples.
- Unit 1: What is the pesticide paradox? Pointer: repeating the same tests stops finding new defects; review tests and add new ones (page 21).
- Unit 2: Normal BVA test cases for the triangle problem, sides 1 to 200. Pointer: 4(3) + 1 = 13 tests, nominal 100, extremes 1, 2, 199, 200 (page 28).
- Unit 3: Build a test execution schedule from priorities and dependencies. Pointer: dependencies first, then highest priority: TC2, TC3, TC4, TC1 (page 49).
- Unit 4: Differentiate TDD, ATDD and BDD. Pointer: unit-level design, story acceptance tests, Given-When-Then behaviour (outline on page 83).
More practice sits in the MCA 120 important questions.
MCA 120 and the GGSIPU MCA Sem 2 papers it connects to
The practical partner of MCA 120 is MCA-168, the lab based on Core Elective I (Software Testing Lab), listed in the GGSIPU MCA syllabus. How the theory units feed the lab's outcomes:
- Unit 4 TDD → CO1, applying test driven development.
- Unit 2 EP, BVA and decision tables → CO2, test cases traced to requirements.
- Unit 3 regression and risk-based prioritisation → CO3, prioritising test cases.
- Unit 3 defect reports and test metrics → CO4, reporting results.
- Unit 4 Scrum and exploratory testing → CO5, an Agile case study.
Other Semester 2 papers: MCA-102 Data and File Structures, MCA-104 Object Oriented Software Engineering, MCA-106 Python Programming, and one Open Elective I from MCA-128 to MCA-134.
Who writes and checks the MCA 120 testing notes?
- Prateek Talwar, author: Founder, Unnati Educations; Associate Company Secretary (ACS), ICSI, membership no. 58704, since 15 May 2019; B.Com, University of Delhi (School of Open Learning), 2012. Author bio
- Ritik Rawat, subject reviewer: B.Tech; Senior Full Stack Developer, Unnati Educations.
These GGSIPU MCA Sem 2 Software Testing notes are mapped to the scheme effective from 2025-26 (BoS USIC&T, 28 July 2025) and follow TB1 Jorgensen. Last updated 14 October 2026; see our editorial policy. The same team prepares GGSIPU important questions for every course.
Do the MCA 120 notes cover the full GGSIPU syllabus?
Yes. Every MCA-120 topic in Units I to IV has a matching section; no gaps were found.
| Official unit | Official topics | Where in the notes | Status |
|---|---|---|---|
| Unit I | Fundamentals of Testing; Testing through the SDLC (test levels); Static Testing | Sections 1-16, pages 6-19 | Covered |
| Unit II | Test Types; Functional Testing (EP, BVA, decision table, state transition, use cases); Structural Testing (CFG to mutation testing) | Sections 1-16, pages 24-40 | Covered |
| Unit III | Test Management; Configuration Management (risks, risk-based testing, priority schemes); Defect Management; Regression Testing | Sections 1-19, pages 45-60 | Covered |
| Unit IV | Test Driven Development; Object-Oriented Testing; Agile Testing (XP, Scrum, TDD, AMDD, tester roles, exploratory testing) | Sections 1-18, pages 66-80 | Covered |
MCA 120 official syllabus vs the notes
- Official unit
- Unit I
- Official topics
- Fundamentals of Testing; Testing through the SDLC (test levels); Static Testing
- Where in the notes
- Sections 1-16, pages 6-19
- Status
- Covered
- Official unit
- Unit II
- Official topics
- Test Types; Functional Testing (EP, BVA, decision table, state transition, use cases); Structural Testing (CFG to mutation testing)
- Where in the notes
- Sections 1-16, pages 24-40
- Status
- Covered
- Official unit
- Unit III
- Official topics
- Test Management; Configuration Management (risks, risk-based testing, priority schemes); Defect Management; Regression Testing
- Where in the notes
- Sections 1-19, pages 45-60
- Status
- Covered
- Official unit
- Unit IV
- Official topics
- Test Driven Development; Object-Oriented Testing; Agile Testing (XP, Scrum, TDD, AMDD, tester roles, exploratory testing)
- Where in the notes
- Sections 1-18, pages 66-80
- Status
- Covered
Official source: MCA Scheme of Examination and Detailed Syllabus, batch 2025-26 onwards (ipu.ac.in).
Every course in GGSIPU notes is mapped to its official PDF the same way.
MCA 120 testing notes FAQs
How do I get the full MCA 120 notes?
Send a WhatsApp message to 9899436384 with the code MCA 120. The full notes come as a printed book only, not as a PDF. Delivery takes 5 to 7 days at most, depending on your location. The sample PDF at the top of this page shows the cover, index and one page from each unit.
What is the passing mark in MCA 120 Software Testing?
MCA 120 is marked out of 100: 60 end-term (12 + 48) and the remaining 40 internal. The MCA scheme of examination states pass marks as 40%, which is 40 out of 100, for every paper. The PDF does not print a separate end-term minimum, so check Ordinance 11 on ipu.ac.in for end-term minimums and re-appear rules.
Is MCA 120 a compulsory paper in MCA Semester 2?
No. MCA 120 Software Testing is one of ten Core Elective I options in Semester 2, alongside Theory of Computations, Web Technologies and others. You choose one, and it carries 4 credits with 3 lecture and 1 tutorial hour a week. If fewer than 20 students choose it, the scheme says it is completed through a MOOC.
Which MCA 120 unit has the most numericals?
Unit 2. It holds 13 of the 19 solved examples: equivalence classes and BVA on the triangle problem, a decision table, a state machine, a use case, and one largest-of-three program used for the flow graph, cyclomatic complexity, graph matrix, data flow and mutation. Unit 3 adds 4 small numericals on scheduling, estimation, risk scores and regression selection.
Do the MCA 120 notes match the 2025-26 MCA scheme?
Yes for topics: every MCA-120 topic in the scheme effective from 2025-26 is covered, as the syllabus map shows. One difference: the question sets are labelled 2.5 Marks and 12.5 Marks, while the 2025-26 paper uses a 12-mark compulsory Q1 and 12-mark unit questions. Use the short answers for Q1 and the long-answer outlines for unit questions.
Do the MCA 120 notes include the MCA-168 Software Testing Lab?
No. These are theory notes for MCA 120. The lab is a separate 1-credit paper, MCA-168, whose outcomes cover TDD, test case design, prioritisation, test reporting and an Agile case study. The MCA 120 theory notes explain the concepts behind those practicals, but they do not contain the lab programs, test scripts, outputs or viva sets.
Get the full MCA 120 Software Testing Notes on WhatsApp
The full notes come as a printed book only, not as a PDF. Order on WhatsApp (9899436384).
What the MCA 120 notes book contains
- Unit
- Unit 1
- Pages
- 5-22 (18)
- Solved examples
- 0
- Exam questions
- 23
- Unit
- Unit 2
- Pages
- 23-43 (21)
- Solved examples
- 13
- Exam questions
- 23
- Unit
- Unit 3
- Pages
- 44-63 (20)
- Solved examples
- 4
- Exam questions
- 24
- Unit
- Unit 4
- Pages
- 64-83 (20)
- Solved examples
- 2
- Exam questions
- 24
- Unit
- Total
- Pages
- 83 incl. cover and index
- Solved examples
- 19
- Exam questions
- 94
Format: printed Software Testing notes in English, with diagrams and a revision sheet per unit. Delivery: within 5 to 7 days at most; the exact time may vary with your location.
Order the full MCA 120 notes book on WhatsApp (4 units, 83 pages)
Unnati Educations is an independent education provider based in Vikaspuri, Delhi. We are not affiliated with, authorised by, or endorsed by Guru Gobind Singh Indraprastha University (GGSIPU). 'GGSIPU' and 'IPU' are used only to describe the syllabus our notes follow. For official information, visit ipu.ac.in.
Ready for the full notes?
Discuss coverage and delivery with our team.