Model Question Paper-1

Software Testing
VI Sem BCA

PART-A
I. Answer any Four questions, each carries Two marks. (4x2=8)

1) What is Software Testing?

Software Testing is a method to assess the functionality of the software program. The
process checks whether the actual software matches the expected requirements and ensures
the software is bug-free. The purpose of software testing is to identify the errors, faults, or
missing requirements in contrast to actual requirements.

2) What is Equivalence Class?

Equivalence classes refer to groups of input values that are treated the same way by the
software system being tested. Test cases are designed to represent each equivalence class to
ensure that the system behaves consistently for all values within that class. This approach
helps in reducing the number of test cases needed while maintaining thorough test
coverage.

3) Define Object Oriented Testing.

Object-Oriented Testing is a software testing process that is conducted to test the software
using object-oriented paradigms like, encapsulation, inheritance, polymorphism, etc. The
software typically undergoes many levels of testing from unit testing to system testing. In
simple words, Object Oriented Testing is a collection of testing techniques to verify and
validate object-oriented software.

4) What is fault and error?

Error:

Error is a situation that happens when the Development team or the developer fails to
understand a requirement definition and hence that misunderstanding gets translated into
buggy code. This situation is referred to as an Error and is mainly a term coined by the
developers.
 Fault:

Sometimes due to certain factors such as Lack of resources or not following proper steps
Fault occurs in software which means that the logic was not incorporated to handle the
errors in the application. This is an undesirable situation, but it mainly happens due to
invalid documented steps or a lack of data definitions.

5) Define sandwich integration.

Sandwich Integration Testing is a hybrid approach that combines elements of both Top-
Down and Bottom-Up Integration Testing strategies. In this method, testing starts
simultaneously from the top (main control modules) and the bottom (individual modules)
towards the middle layers of the software system. The idea is to integrate and test modules
at both ends while gradually moving towards the center of the system, where the
integration of components from both directions occurs.

6) Define weak normal equivalence class testing.

Weak Normal Equivalence Class Testing (WNECT) is a software testing technique that
assumes a single fault and concentrates on testing valid inputs only. It is called "weak"
because it assumes that any failure is caused by a problem in just one input variable at a
time. It is specifically designed to verify the system's behavior under normal operating
conditions with valid input values. It simplifies the testing process and ensure
comprehensive coverage of different input categories.

PART-B
II. Answer any Four questions, each carries Five marks. ( 4 x 5 = 20 )

7) Explain Top down and Bottom up integration.

8) Explain model-based testing.
9) Explain Retrospective on MDD & TDD.
10) Discuss Structure based testing.
11) Explain next date function complexities.
12) What are the types of Boundary value testing?

PART C
III. Answer any Four questions, each carries Eight marks. ( 4 x 8 = 32 )

13) Explain SATM.

14)Explain STLC.
14) Explain object-oriented testing.

Object-Oriented Testing is a software testing process that is conducted to test the software
using object-oriented paradigms like, encapsulation, inheritance, polymorphism, etc. The
software typically undergoes many levels of testing from unit testing to system testing. In
simple words, Object Oriented Testing is a collection of testing techniques to verify and
validate object-oriented software.

As information systems are becoming more complex, the object-oriented paradigm is

gaining popularity because of its benefits in analysis, design, and coding. Conventional
testing methods cannot be applied for testing classes because of problems involved in
testing classes, abstract classes, inheritance, dynamic binding, message passing,
polymorphism, concurrency, etc.

Different Techniques used in object-oriented testing are as follows:

1. Fault Based Testing: This type of checking permits for coming up with test cases
supported the consumer specification or the code or both. It tries to identify possible
faults (areas of design or code that may lead to errors.). For all of these faults, a test
case is developed to “flush” the errors out. These tests also force each time of code to
be executed. This method of testing does not find all types of errors. However,
incorrect specification and interface errors can be missed. These types of errors can
be uncovered by function testing in the traditional testing model. In the object-
oriented model, interaction errors can be uncovered by scenario-based testing. This
form of Object oriented-testing can only test against the client’s specifications, so
interface errors are still missed.
2. Class Testing Based on Method Testing: This approach is the simplest approach to
test classes. Each method of the class performs a well defined cohesive function and
can, therefore, be related to unit testing of the traditional testing techniques.
Therefore all the methods of a class can be involved at least once to test the class.
3. Random Testing: It is supported by developing a random test sequence that tries the
minimum variety of operations typical to the behavior of the categories
4. Partition Testing: This methodology categorizes the inputs and outputs of a category
so as to check them severely. This minimizes the number of cases that have to be
designed.
5. Scenario-based Testing: It primarily involves capturing the user actions then
stimulating them to similar actions throughout the test. These tests tend to search out
interaction form of error.
16) Explain ten best practices for software testing excellence.
17) Explain Interaction in single processor.
18)Explain pros and cons of test-driven development.
 Model Question Paper-2
Software Testing
VI Sem BCA

PART-A
I. Answer any Four questions, each carries Two marks. (4x2=8)

1) Define Software testing.

Software Testing is a method to assess the functionality of the software program. The
process checks whether the actual software matches the expected requirements and ensures
the software is bug-free. The purpose of software testing is to identify the errors, faults, or
missing requirements in contrast to actual requirements.

2) What are Equivalence classes?

Equivalence classes refer to groups of input values that are treated the same way by the
software system being tested. Test cases are designed to represent each equivalence class to
ensure that the system behaves consistently for all values within that class. This approach
helps in reducing the number of test cases needed while maintaining thorough test
coverage.

3) What is thread?

A thread in system testing is a sequence of interconnected Atomic System Functions

(ASFs) that together accomplish a specific user task or workflow in a system. It includes
all the steps a user takes to achieve a particular outcome to ensure that the system correctly
executes the complete sequence of operations required.

4) What is composition?

Composition is one of the fundamental concepts in object-oriented programming. It describes a

class that references one or more objects of other classes in instance variables. This allows you
to model a has-a association between objects.

5) Define exploratory testing.

Exploratory testing is an approach to software testing where testers simultaneously design

and execute test cases based on their domain knowledge, experience and intuition. Unlike
traditional scripted testing, exploratory testing involves testers exploring the software
application dynamically, without predefined test cases, testers learn about the application
as they test, uncovering defects, understanding functionalities, and identifying potential
 risks through an iterative and explorative approach. The goal of exploratory testing is to
discover issue that might not been found through structured testing techniques.

6) Define SATM.

The Simple ATM System (SATM) serves as a practical example to illustrate the
complexities involved in integration and system testing of a client-server architecture. With
a set of functionalities captured in a series of interactive screens, the SATM system
provides an ideal case to examine how different components within an ATM interface
work together to handle user transactions seamlessly.

PART-B
II. Answer any Four questions, each carries Five marks. ( 4 x 5 = 20 )

7) Explain slice-based testing.

8) Explain Top down and Bottom up integration.
9) Explain the features of JUnit.
10) Discuss Testing Life Cycle.
Refer (model 1 ,14th)
11) Explain special value testing.
12) Explain weak normal and strong normal equivalence testing.
 PART C
III. Answer any Four questions, each carries Five marks. (4 x 8 = 32)

13) Explain the characteristics of Dataflow testing.

14) Explain test-then code cycle.
 15) Explain pros and cons of test-driven development.
Refer model paper 1
16) Explain ten best practices for software testing excellence
Refer model paper 1 ,16th
17) Explain test cases of Commission problem.
18) Explain Boundary value testing.