Mumbai University Solved Question Papers
Software Testing and Quality Assurance
Previous Year Question Paper with Solution
BSc CS · Sem 5
2023-24 Examination
munotes.in
Mumbai
BSc CS Sem 5 Software Testing and Quality Assurance 2023-24 Question Paper with Solutions
Get access to whole semester resourcesSemester Pass
MU B.Sc. (Computer Science) student group
Free to join
First published on munotes.in on 17 October 2026.
Published by munotes.in, Mumbai.
Model answers written and edited by the munotes.in editorial desk.
Passages from this volume may be quoted, in print, online or by an AI system, with credit: name munotes.in and link to this volume's page. The volume may not be reproduced as a whole. Full terms at munotes.in/content-license.
munotes.in is an independent study resource for students of the University of Mumbai. It is not affiliated with the University of Mumbai, and is not endorsed by it.
The University does not publish an official answer key for this paper. The answers in this volume are model answers, written to show how a full-mark answer is built. They are a study aid, not an authority on what an examiner marked.
The question paper reproduced here is the paper as set by the University of Mumbai at the 2023-24 examination.
Contents
The questions below are the paper as the University of Mumbai set it at the 2023-24 examination, in the order it was set.
MarksPage
MarksPage
The Paper as Set
The questions in this volume are the questions asked at the 2023-24 examination, reproduced as the University of Mumbai set them, in the order it set them. Nothing has been reworded, added or left out. Only the answers are ours. See the original question paper.
Duration 2½ hours · Total marks 75 · 24 questions answered
Instructions printed on the paper
- N.B. (1) All questions are compulsory. (2) Figures to the right indicate marks. (3) Illustrations, in-depth answers and diagrams will be appreciated. (4) Mixing of sub-questions is not allowed.
How to use this volume
Solve the paper first, under exam conditions and against the clock. Then read the answers here and mark your own. Reading a solution before attempting the question feels productive and teaches very little, because recognising an answer is not the same as being able to write one.
SECTION I
Q.1
Attempt ANY FOUR from the following · 20 Marks
(a)What is an error? Explain Types of Errors.[5]
Answer
For full marks, cover: the definition of an error and how it leads to a fault and a failure, the types of error by the phase in which they are made, the types by their nature with examples, and why the type matters.
What an error is
An error is a human action that produces an incorrect result: a mistake made by a person, such as a misunderstood requirement or a wrong formula typed into code.
The chain is:
- A person makes an error (mistake).
- The error puts a fault (also called a defect or bug) into a work product: the requirements, design or code.
- When the faulty code runs under certain conditions, it causes a failure: the system does not do what it should.
Not every fault causes a failure; a fault in code that never runs stays hidden.
Types of error by phase
- Requirement errors: missing, ambiguous or wrong requirements, such as a fee rule stated incompletely. These are the most costly, because everything built on them is wrong.
- Design errors: wrong architecture, wrong algorithm or wrong interface between modules.
- Coding errors: mistakes in writing the program.
- Testing errors: wrong test cases or wrong expected results, which hide real faults.
- Documentation errors: user manuals or help text that do not match the system.
Types of error by nature
- Syntax errors: break the language rules, such as a missing bracket. The compiler catches them.
- Logic errors: the program runs but gives the wrong answer, such as using
>where>=was needed. - Calculation (computation) errors: wrong formula, rounding or overflow.
- Runtime errors: the program crashes while running, such as division by zero or a null reference.
- Interface errors: modules pass data in the wrong format or order.
- Boundary errors: failures at the edges of ranges, such as an off-by-one loop.
- Data handling errors: wrong initialisation, wrong type or lost data.
- User interface errors: confusing messages, wrong navigation, missing validation.
Why the type matters
The type tells testers where to look and which technique to use: boundary value analysis targets boundary errors, reviews target requirement and design errors, and integration testing targets interface errors. It also guides process improvement, because a type that keeps recurring points to a weak step in development.
Conclusion. An error is a human mistake that introduces a fault, which may cause a failure when the faulty part runs. Errors are classed by phase (requirement, design, coding, testing, documentation) and by nature (syntax, logic, calculation, runtime, interface, boundary, data and user interface), and the type guides both testing and improvement.
The rest of the answers
The first answer is free. The rest come with the B.Sc. (Computer Science) Semester 5 solved papers.
You have read the question paper and its first answer in full. Buy the solved papers once and you can read every answer of every solved paper in this semester.
Notes + practical solutions + solved papers: ₹798 Already bought it? Sign in
Or solved papers only: ₹499
Or notes + practical solutions: ₹499
The question paper itself stays free, and so does the syllabus.
Found an error in this volume? Report it and we will check it against the paper.