(SEM VII) THEORY EXAMINATION 2018-19 SOFTWARE TESTING AND AUDIT

SECTION A

Attempt all questions in brief (2 × 10 = 20 marks)

(a) What is SDLC?

SDLC stands for Software Development Life Cycle. It is a systematic process used to develop software in a structured and disciplined way. It includes phases such as requirement analysis, design, development, testing, deployment, and maintenance. SDLC ensures quality software is delivered within time and budget.

(b) Define validation in software testing

Validation is the process of checking whether the developed software meets the user’s requirements. It answers the question, “Are we building the right product?” Validation is usually done through testing the actual software.

(c) When do we use decision table testing?

Decision table testing is used when the system behavior depends on multiple input conditions and different combinations of those conditions produce different outcomes. It is useful for testing business rules and complex logic.

(d) What is test case?

A test case is a set of conditions or inputs, execution steps, and expected results designed to verify that a specific function of software works correctly.

(e) What is black box testing?

Black box testing is a software testing technique where the tester checks the functionality of the software without knowing the internal code structure. The focus is on input and output behavior.

(f) Define white box testing

White box testing is a testing method in which the tester has knowledge of the internal code, logic, and structure of the program. It focuses on code coverage and internal paths.

(g) What is regression testing?

Regression testing is performed to ensure that new changes or bug fixes have not affected the existing functionality of the software.

(h) What is software audit?

A software audit is a systematic examination of software processes, products, and documentation to ensure compliance with standards, procedures, and contractual requirements.

(i) What is defect?

A defect is a flaw or error in software that causes it to produce incorrect or unexpected results or behave differently than expected.

(j) What is test plan?

A test plan is a formal document that describes the scope, objectives, approach, resources, and schedule of testing activities in a project.

SECTION B

Attempt any one part (10 × 1 = 10 marks)

(a) What is Functional Testing? Why is it important?

Functional Testing is a type of software testing that verifies whether the software functions according to the specified requirements. It focuses on testing each function of the software by providing appropriate input and examining the output.

Functional testing does not consider how the software is implemented internally. Instead, it checks whether the system behaves correctly from the user’s point of view.

Importance of Functional Testing:
Functional testing is important because it ensures that the software performs all intended operations correctly. It helps detect missing functions, incorrect behavior, interface errors, and incorrect data handling. Without functional testing, software may fail to meet user expectations, even if it is technically well coded.

(b) What are the basic differences between Data Flow Testing and Mutation Testing?

Data Flow Testing focuses on the lifecycle of variables in a program, such as where they are defined, used, and modified. It checks for issues like uninitialized variables and incorrect variable usage.

Mutation Testing, on the other hand, evaluates the quality of test cases by introducing small changes (mutations) into the program code. The goal is to check whether existing test cases can detect these changes.

Key Difference:
Data Flow Testing improves code correctness, while Mutation Testing measures the effectiveness of test cases.

SECTION C

Attempt any one part (10 × 1 = 10 marks)

(a) What is Verification and Validation in software testing? Differentiate between them.

Verification is the process of evaluating work products such as documents, design, and code to ensure they meet specified requirements. It answers the question, “Are we building the product right?” Verification does not involve executing the software.

Validation is the process of evaluating the actual software to ensure it meets user needs. It answers the question, “Are we building the right product?” Validation involves executing the software.

Difference between Verification and Validation:

(b) Define SRS. What is source code review and user documentation verification?

SRS (Software Requirement Specification) is a formal document that describes the functional and non-functional requirements of a software system. It acts as a contract between the client and the development team.

Source Code Review is a systematic examination of source code to identify errors, improve code quality, and ensure adherence to coding standards.

User Documentation Verification ensures that manuals, help files, and guides are accurate, clear, and consistent with the actual software behavior.