BCA 204T Software Testing Notes from Unnati Educations cover all 4 units of this IPU BCA Semester 4 paper in 89 pages: 61 solved two-mark answers, 34 ten-mark questions mapped to the sections that answer them, 8 solved test-design examples and 26 figures. They follow the scheme for the batch admitted in 2024-25 onwards.
Written by Prateek Talwar, Founder, Unnati Educations · Reviewed by Ritik Rawat, B.Tech, Senior Full Stack Developer · Checked against the official BCA Scheme and Syllabus, notice of 04 Aug 2025 · Updated 13 October 2026 · Editorial policy
Scheme: BCA scheme w.e.f. 2024-25 | Applies to: batch admitted 2024-25 onwards | Verified against: BCA Scheme and Syllabus (1st and 2nd Year Common), 04 Aug 2025
On this page
BCA 204T Software Testing at a glance: GGSIPU BCA Sem 4 credits, units and exam pattern
| Paper | BCA 204T Software Testing, BCA Semester 4 |
|---|---|
| Category and credits | Core Course Theory (CCT), 4 credits, 4 lecture hours a week |
| Marks | 100: 40 internal + 60 end-term |
| Applies to | Batch admitted 2024-25 onwards |
| End-term pattern | Q1: 10 two-mark questions, 2+ per unit; then one 10-mark question per unit (20 + 40 = 60 marks) |
| Units | 4, 11 teaching hours each |
| Pass rules | No pass % printed; see GGSIPU Ordinance 11 |
| Paired lab | BCA 204P Software Testing Lab: CCP, 2 practical hours, 1 credit, 100 marks (40 + 60) |
BCA 204T and Operating Systems are the core theory papers of this 23-credit semester. See the GGSIPU BCA Semester 4 papers.
BCA 204T Software Testing Notes unit-wise: 61 solved two-mark answers and 8 solved examples across 4 units
These BCA 204T Software Testing IPU notes give each unit its own block of solved two-mark answers, a ten-mark list and a common-mistakes table. Other papers' notes sit under GGSIPU BCA notes.
BCA 204T Unit 1: Introduction to Software Testing
Why exhaustive testing is impossible, the seven principles, and the error, fault, failure, incident chain. Beizer's severity scale and fault types lead into test cases, the six-phase STLC, the V-model and three review types: inspection, walkthrough and technical review. Pages 4 to 26, 7 figures, 16 two-mark answers, 9 ten-mark questions.
Quick look: a pass-mark bug, step by step (from page 9)
| Error | Programmer thinks a pass means marks above 40 |
|---|---|
| Fault | if (marks > 40) instead of >= 40 |
| Failure | Entering 40 prints FAIL |
| Incident | The student complains; a bug report is raised |
BCA 204T Unit 2: Functional and Structural Testing
Black box: four BVA variants, four types of equivalence class testing and decision tables, worked on the triangle problem and NextDate. White box: one C loop becomes a program graph, a 7-node DD-path graph, V(G) = 3 by three methods and data flow du-paths. Pages 27 to 54, 8 figures, all 8 solved examples, 16 two-mark answers, 8 ten-mark questions.
Quick look: equivalence class test counts (from page 32)
| Weak normal | max(3, 2) = 3 tests |
|---|---|
| Strong normal | 3 x 2 = 6 tests |
| Weak robust | 3 + 4 invalid = 7 tests |
| Strong robust | 5 x 4 = 20 tests |
BCA 204T Unit 3: Levels of Testing
Unit testing with stubs and drivers, then integration: big bang, top-down (6 stubs for the 7-module example), bottom-up (3 drivers), sandwich, call graph and MM-path. System testing covers ten numbered non-functional categories; acceptance testing covers its criteria and seven types, including alpha versus beta. Pages 55 to 71, 6 figures, 15 two-mark answers, 8 ten-mark questions.
Quick look: driver versus stub (from page 58)
| Basis | Driver | Stub |
|---|---|---|
| Role | Calls the unit | Is called by the unit |
| Used in | Bottom-up | Top-down |
| Example | main() calling calculate_tax(50000) | get_rate() returning 10 |
Quick look: driver versus stub (from page 58)
- Basis
- Role
- Driver
- Calls the unit
- Stub
- Is called by the unit
- Basis
- Used in
- Driver
- Bottom-up
- Stub
- Top-down
- Basis
- Example
- Driver
main()callingcalculate_tax(50000)- Stub
get_rate()returning 10
BCA 204T Unit 4: Test Planning and Test Management
The 16 sections of an IEEE 829 test plan, scope, test approach (for an online exam portal), the four kinds of criteria, staffing, resources and estimation. Then TCDB, defect repository, SCM, traceability and the three test reports. Pages 72 to 89, 5 figures, 14 two-mark answers, 9 ten-mark questions.
Quick look: a traceability matrix exposing a gap (from page 85)
| R1 Log in | TC01 to TC03: Passed |
|---|---|
| R2 Lock after 3 tries | TC04: Failed (Bug #17) |
| R5 Download result PDF | No test case: gap found |
BCA 204T exam corner: 61 two-mark answers and 34 ten-mark questions by unit
| Unit | 2 Marks (solved) | 10 Marks (mapped) | Solved examples |
|---|---|---|---|
| 1 | 16 | 9 | 0 |
| 2 | 16 | 8 | 8 |
| 3 | 15 | 8 | 0 |
| 4 | 14 | 9 | 0 |
BCA 204T questions and examples in the notes
- Unit
- 1
- 2 Marks (solved)
- 16
- 10 Marks (mapped)
- 9
- Solved examples
- 0
- Unit
- 2
- 2 Marks (solved)
- 16
- 10 Marks (mapped)
- 8
- Solved examples
- 8
- Unit
- 3
- 2 Marks (solved)
- 15
- 10 Marks (mapped)
- 8
- Solved examples
- 0
- Unit
- 4
- 2 Marks (solved)
- 14
- 10 Marks (mapped)
- 9
- Solved examples
- 0
The BCA 204T notes solve 61 two-mark questions and list 34 ten-mark questions across 4 units, plus 8 solved test-design examples.
Four exam-style two-mark questions, one per unit:
- Testing versus debugging? Testing finds failures; debugging locates and removes the fault.
- Cyclomatic complexity formula? V(G) = e - n + 2P = predicate nodes + 1 = number of regions.
- Load versus stress testing? Load stays within peak load; stress goes past it to find the breaking point.
- Suspension versus resumption criteria? When to pause testing (blocking defect) and when to restart (new build passes the smoke test).
Practise more in the BCA 204T important questions.
Who writes and checks the BCA 204T testing notes?
- Prateek Talwar, author: Founder, Unnati Educations; ACS (ICSI) since 2019; B.Com, University of Delhi, 2012. Author bio
- Ritik Rawat, subject reviewer: B.Tech, Senior Full Stack Developer; checks every BCA 204T technique and worked count. Reviewer bio
The 2026-27 edition follows the 2024-25 batch scheme, last checked on 13 October 2026, and includes robust BVA rows for the triangle problem and the 26 = 64 rule check for its decision table. Our editorial policy explains how errors are fixed.
The same team prepares GGSIPU important questions for every course.
How to write BCA 204T answers: test-case tables, V(G) working and ten-mark comparison answers
BCA 204T answers come in three shapes: a test-case table, a worked graph problem and a ten-mark theory answer that ends in a comparison table.
Test-case tables. State the range, list min, min+, nom, max- and max, give the formula (4n + 1 for normal BVA, 6n + 1 for robust), then the table with an expected-output column. The notes warn against writing 4n, and against using 0 and 101 in normal BVA for 1 to 100.
Graph problems. The DD-path tip: give the three-column mapping table before the drawing, since it earns marks even if the graph is small. For V(G), show all three methods and say they agree.
Worked example (page 45): "largest of three numbers" with nested if-else: 9 nodes, 11 edges, 3 decision nodes.
V(G) = e - n + 2P = 11 - 9 + 2(1) = 4
V(G) = decision nodes + 1 = 3 + 1 = 4
4 independent paths, at least 4 test casesTen-mark theory. For fault taxonomies: meaning, severity table, fault types with two examples each, then why taxonomies help. For release recommendation, end with "testing gives information, not guarantees". For decision tables, add the rule count check.
These GGSIPU BCA Sem 4 Software Testing notes keep two-mark answers to two or three lines. Practise the format on GGSIPU BCA important questions.
BCA 204T and the BCA 204P Software Testing lab (15 practicals), plus other GGSIPU BCA Sem 4 papers
BCA 204P Software Testing lab notes: 15 core practicals in the official list, each mapped to a course outcome; 1 credit.
Our grouping of practicals:
- Unit 1 → practicals 1 to 5: bug classification, test documents, STLC, V&V, code review.
- Unit 2 → practicals 6 to 10: BVA on age 1 to 100, mobile-number classes, a login decision table, cyclomatic complexity.
- Unit 3 → practicals 11 to 14: unit, integration, system and acceptance tests.
- Unit 4 → practical 15: a full test plan.
Other Semester 4 papers: BCA 202T Operating Systems and BCA 202P Operating Systems Lab; BCA 232 Introduction to Logic and Critical Thinking; BCA 234 Health and Wellness, Yoga Education and Sports and Fitness (NUES).
One elective pair: BCA 212T/212P Introduction to Data Science, BCA 216T/216P Introduction to Security, Acts and Cyber Laws and Cyber Security, BCA 218T/218P Web Development Using Python, or BCA 220T/220P Information Security. One generic elective: BCA 222T Digital Marketing, BCA 224T Principles of Accounting or BCA 226T Open Elective.
The official prerequisite is BCA 108T Software Engineering (Semester 2), whose Unit IV introduces testing.
Verification and validation in software testing: excerpt from page 16 of the BCA 204T notes
Excerpt from page 16
V&V is the general name for all the checking activities in software development. Barry Boehm explained the difference between the two halves with two simple questions, and Figure 1.4 on this page shows them side by side. Verification asks "Are we building the product right?" Validation asks "Are we building the right product?"
Verification
Verification is the process of checking whether the output of a development phase meets the conditions that were set at the start of that phase, that is, the document produced by the previous phase. It checks documents, design and code without executing the program. The work is done through reviews, walkthroughs and inspections, so verification is static testing.
Validation
Validation is the process of checking the final software against the user requirements at the end of development, to confirm that it really does what the users need. It involves executing the software through unit, integration, system and acceptance testing, so validation is dynamic testing.
| Basis | Verification | Validation |
|---|---|---|
| Question | Are we building the product right? | Are we building the right product? |
| Type | Static (no execution) | Dynamic (code executed) |
| Checks | Documents, design, code | The actual working product |
| Methods | Reviews, walkthroughs, inspections | Black box and white box testing |
| Done by | QA team, developers, reviewers | Testing team, and users in UAT |
| When | Before validation, in every phase | After a build or product is ready |
| Finds | Bugs early, when they are cheaper to fix | Bugs that verification missed |
| Target | Process and intermediate products | The final product |
| Example | Reviewing the SRS for missing requirements | Running the app to check that login works |
Verification versus validation (excerpt, page 16)
- Basis
- Question
- Verification
- Are we building the product right?
- Validation
- Are we building the right product?
- Basis
- Type
- Verification
- Static (no execution)
- Validation
- Dynamic (code executed)
- Basis
- Checks
- Verification
- Documents, design, code
- Validation
- The actual working product
- Basis
- Methods
- Verification
- Reviews, walkthroughs, inspections
- Validation
- Black box and white box testing
- Basis
- Done by
- Verification
- QA team, developers, reviewers
- Validation
- Testing team, and users in UAT
- Basis
- When
- Verification
- Before validation, in every phase
- Validation
- After a build or product is ready
- Basis
- Finds
- Verification
- Bugs early, when they are cheaper to fix
- Validation
- Bugs that verification missed
- Basis
- Target
- Verification
- Process and intermediate products
- Validation
- The final product
- Basis
- Example
- Verification
- Reviewing the SRS for missing requirements
- Validation
- Running the app to check that login works
Easy trick
Verification = View the documents (nothing is run). Validation = action (the software is run). Keep the two questions in mind, and the rest of the whole table then follows from them.
Do the BCA 204T notes cover the full GGSIPU syllabus?
Yes: every topic in Units I to IV of the official BCA 204T syllabus has its own section. Learning objective 3 mentions object-oriented and internet-based testing, but no unit lists it, so the notes skip it.
| Unit | Official topics | In the notes | Status |
|---|---|---|---|
| I | Testing and why it is hard, goals, principles, error to incident, taxonomies, test cases, STLC, V-testing, limitations, static and dynamic, inspection, walkthrough, technical review | 1.1 to 1.16, pp 5 to 23 | Covered |
| II | Black box, BVA, equivalence class, decision table; white box, need of white box, path testing, DD-paths, cyclomatic complexity, graph metrics, data flow testing | 2.1 to 2.10, pp 28 to 51 | Covered |
| III | Unit, integration, system testing and its categories, acceptance testing and its types | 3.1 to 3.6, pp 56 to 68 | Covered |
| IV | Test plan, scope, approach, criteria, staffing, training, resources, deliverables, tasks; infrastructure, people, release, test process, traceability, reporting | 4.1 to 4.13, pp 73 to 87 | Covered |
BCA 204T official topics mapped to the notes
- Unit
- I
- Official topics
- Testing and why it is hard, goals, principles, error to incident, taxonomies, test cases, STLC, V-testing, limitations, static and dynamic, inspection, walkthrough, technical review
- In the notes
- 1.1 to 1.16, pp 5 to 23
- Status
- Covered
- Unit
- II
- Official topics
- Black box, BVA, equivalence class, decision table; white box, need of white box, path testing, DD-paths, cyclomatic complexity, graph metrics, data flow testing
- In the notes
- 2.1 to 2.10, pp 28 to 51
- Status
- Covered
- Unit
- III
- Official topics
- Unit, integration, system testing and its categories, acceptance testing and its types
- In the notes
- 3.1 to 3.6, pp 56 to 68
- Status
- Covered
- Unit
- IV
- Official topics
- Test plan, scope, approach, criteria, staffing, training, resources, deliverables, tasks; infrastructure, people, release, test process, traceability, reporting
- In the notes
- 4.1 to 4.13, pp 73 to 87
- Status
- Covered
Source: Official BCA scheme and syllabus, batch 2024-25 onwards (BCA 204T on page 94).
Every course in GGSIPU notes is mapped to its official PDF the same way.
BCA 204T testing notes FAQs
How do I get the full BCA 204T notes?
Order them on WhatsApp. Tap "Get Full Notes" at the top of this page or the button at the end, and a chat opens with our desk with your paper code already typed. The full BCA 204T notes come only as an 89-page printed book; there is no PDF edition. We confirm the price and delivery details in the chat.
Do the BCA 204T notes match the batch admitted in 2024-25?
Yes. The BCA 204T notes follow the scheme that applies to students admitted in the 2024-25 session onwards, checked against the official scheme and syllabus notice of 04 August 2025. All four units and every topic under them are mapped in the syllabus table above. On an older scheme, compare its unit list with that table first.
What is the passing mark for BCA 204T?
BCA 204T is marked out of 100: 40 internal and 60 in the end-term exam. The official BCA scheme and syllabus does not print a pass percentage for this paper; its 40% line applies only to the NUES bridge course. Minimum marks, grading and re-appear rules come from the university's Ordinance 11 on ipu.ac.in, so check that ordinance.
Which BCA 204T unit has the most solved examples?
Unit 2 of BCA 204T holds all 8 solved examples in the notes and is also the longest unit at 28 pages. They cover BVA on the triangle problem and an age field, equivalence classes for the triangle problem and NextDate, the triangle decision table, cyclomatic complexity, a practice V(G) question and du-paths for a running C program.
Is BCA 204T the same as the BCA 204P Software Testing Lab?
No. BCA 204T is the 4-credit theory paper with a written end-term exam, and these notes are for it. BCA 204P is the separate 1-credit practical paper with its own 15-practical list, such as BVA on an age field and a login decision table. The lab applies BCA 204T techniques, so these notes help with viva answers too.
Do the BCA 204T notes cover object-oriented and web application testing?
Only briefly. The BCA 204T learning objectives mention testing object-oriented and internet-based applications, but none of the four official units lists it as a topic. The notes follow the unit topics, so they touch it only in passing, for example grey box testing for web applications and compatibility testing on browsers. There is no dedicated section.
Get the full BCA 204T Software Testing Notes on WhatsApp
| Unit | Pages | Count |
|---|---|---|
| Cover and contents | 1 to 3 | 3 |
| Unit 1 | 4 to 26 | 23 |
| Unit 2 | 27 to 54 | 28 |
| Unit 3 | 55 to 71 | 17 |
| Unit 4 | 72 to 89 | 18 |
Pages per unit in the BCA 204T notes book
- Unit
- Cover and contents
- Pages
- 1 to 3
- Count
- 3
- Unit
- Unit 1
- Pages
- 4 to 26
- Count
- 23
- Unit
- Unit 2
- Pages
- 27 to 54
- Count
- 28
- Unit
- Unit 3
- Pages
- 55 to 71
- Count
- 17
- Unit
- Unit 4
- Pages
- 72 to 89
- Count
- 18
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.