SOFTWARE TESTING

ASSIGNMENT

2 MARKS QUESTION’S

1. DEFINE SOFTWARE TESTING.

Software testing is a process of identifying the correctness of
software by considering its all attributes and evaluating the
execution of software components to find the software bugs or errors
or defects.
2. WHAT IS EQUIVALENCE CLASS TSTING (ECT)? GIVE AN
EXAMPLE.
Equivalence Class Testing (ECT) is a software testing technique that
divides input data into partitions of equivalent classes. Each class
represents a set of inputs that are expected to be treated similarly by
the system. Testing one representative value from each class
assumes that the entire class behaves similarly. Example: A valid
password must be between 8 to 16 characters long
3. WHAT IS DEFINE-USE TESTING?
Define-use testing is a software testing technique focused on
identifying and examining the use of variables in code. It involves
tracing the points where variables are defined (assigned values) and
where these values are subsequently used.
4. WHAT IS TOP DOWN INTEGRATION TESTING?
Top-down integration testing begins with testing the top-level
modules and progressively integrates lower-level modules. Stubs,
which simulate the behaviour of missing modules, are used initially.
This approach helps identify major issues early and ensures critical
modules are tested first.
5. WHAT IS CLIENT SERVER TESTING?
Client-server testing evaluates interactions between a client application
and a server, ensuring proper communication, data exchange,
performance, security, and functionality across the network for reliable
and efficient operations.
6. WHAT IS OBJECT ORIENTED TESTING?
Object-oriented testing evaluates software designed using object-
oriented principles, focusing on testing classes, objects, inheritance,
polymorphism, and encapsulation to ensure proper functionality,
interaction, and behaviour of the objects and methods.
7. DEFINE TEST AND TESTCASE?
A test is an evaluation process to determine if software functions
correctly. A test case is a specific set of conditions and inputs used to
verify a particular aspect of the software's behaviour and output.
8. WHAT IS DECISION TABLE BASED TESTING
Decision table-based testing is a systematic technique where inputs and
their associated conditions are organized in a table format to validate
software behaviour under various combinations of input conditions.
9. WHAT IS SLICE BASED TESTING?
Slice-based testing is a method where a subset (slice) of the software's
functionality is isolated for testing. This approach aims to thoroughly
test specific features or modules without the need to test the entire
system.
10. WHAT IS CALL GRAPH-BASED INTEGRATION?
Call graph-based integration analyses function call relationships within
a program to enhance understanding, impact analysis, test case
generation, code optimization, refactoring, and detection of dead code
11 .WHAT IS EXPLORATORY TESTING?
Exploratory testing involves simultaneously learning, designing, and
executing tests to discover defects and understand the software's
functionality without predefined test cases, emphasizing tester
creativity and intuition.
12 .WHAT IS TEST-THEN-CODE CYCLE?
The test-then-code cycle involves writing tests before implementing
code, ensuring functionality meets requirements. It promotes early
defect detection, guiding development with tests.
13. WHAT IS SPECIFIC BASED TESTING? GIVE EXAMPLE?
Specific-based testing focuses on predefined, detailed test cases
targeting particular functionalities or requirements. Example, testing
login functionality with valid and invalid credentials to ensure correct
behaviour
14. WHAT IS WEAK ROBUST EQUIVALENCE CLASS
TESTING (WRECT)?
Weak Robust Equivalence Class Testing (WRECT) is a software
testing technique that combines equivalence class partitioning and
robustness testing to evaluate both valid and invalid input conditions
using boundary values and representative cases.
15. DEFINE DU-PATH AND DC PATH?
DU Path: handles real-time processing tasks between the Radio Unit
and Central Unit in 5G networks.
DC Path: In 5G networks refers to the distributed core network
functions enhancing efficiency and performance.
16 .WHAT IS PATH-BASED INTEGRATION TESTING?
Path-based integration testing involves verifying interactions between
modules or components based on defined execution paths through the
system, ensuring proper functionality and detecting integration issues
early in software development.
17. WHAT IS USE CASE BASED TESTING?
Deriving test cases directly from the functional requirements specified
in use cases. It ensures that the software behaves correctly in real-world
scenarios as defined by user interactions and system responses.
18. WHAT IS TEST DRIVEN DEVELOPMENT (TDD)?
Test-Driven Development (TDD) is a software development approach
where tests are written before the actual code. Developers iteratively
write failing tests, then write code to pass those tests, ensuring code
correctness and reliability from the start.
19. WHAT IS CODE BASED TESTING? GIVE AN EXAMPLE.
Code-based testing involves directly assessing code for correctness,
efficiency, and reliability. An example is unit testing, where individual
functions or methods are tested to ensure they produce expected results
under various conditions.
20. WHAT IS DATA FLOW TESTING?
Data flow testing is a white-box testing technique that analyses paths
through the program based on the flow of data. It ensures that data is
properly transmitted and transformed between variables and modules,
detecting potential errors in data handling.
21. WHAT IS PAIR WISE INTEGRATION TESTING?
Where pairs of components or modules are tested together to identify
interaction defects efficiently. This approach ensures comprehensive
coverage while minimizing the number of test cases needed.
22. WHAT IS A THREAD IN SYSTEM TESTING?
In system testing, a thread refers to a sequence of tasks or actions that
are executed to simulate a specific user scenario or system
functionality. Threads help validate end-to-end system behaviour under
various operational conditions.
23. WHAT ARE TAXONOMY OF INTERACTIONS?
Taxonomy of interactions refers to categorizing interactions between
components or systems based on their nature, purpose, and impact. It
helps in identifying and prioritizing testing efforts to ensure
comprehensive integration and system functionality validation.
24. WHAT IS MODEL BASED TESTING (MBT)?
Model-Based Testing (MBT) is a technique where test cases are
derived from models that represent the desired behaviour of the system.
It helps automate test generation and ensures test coverage based on
specified models of system behaviour.
.