1) Explain the term Performance Testing:

Performance testing checks the speed, stability, and scalability of software under a specific workload. It ensures the system
responds quickly and remains stable under stress. Types include Load Testing, Stress Testing, and Soak Testing. The main goal is
to identify bottlenecks before deployment.

2) Define Big Bang Approach:

In Big Bang Integration Testing, all modules are combined and tested as a whole after development. It’s simple but risky, as it's
difficult to trace defects. It is used when the system is small or integration is done late. Major drawback is the lack of
incremental testing.

3) Define Software Review:

Software Review is a quality assurance activity where software documents or code are examined by developers or testers. It
identifies issues before testing begins. Types include peer reviews, walkthroughs, and formal inspections. It improves software
quality and reduces rework.

4) Define Failure and Defect:

 Defect: A flaw or error in the software code or design.
 Failure: Occurs when a defect causes the software to behave incorrectly during execution. Defects may or may not lead
to failures depending on the execution path.

5) Define the term SQA:

SQA (Software Quality Assurance) is a set of processes to ensure software quality throughout development. It includes
standards, audits, reviews, and process monitoring. SQA aims to prevent defects rather than detect them after development.

6) Explain Sandwich Approach:

The Sandwich (Hybrid) approach combines Top-Down and Bottom-Up integration testing. It tests middle layers first, followed by
both top and bottom layers. It’s useful when development is done in parallel and both control and utility modules need early
validation.

7) What is Dynamic Testing?

Dynamic testing is performed by executing the program code. It checks the functional behavior, performance, and interaction of
software modules. Examples include unit testing, integration testing, system testing, and acceptance testing. It validates the
runtime behavior of software.

8) Explain terms - Error, Fault, and Failure:

 Error: Human mistake in coding or logic.
 Fault (Defect): A bug introduced due to an error in code.
 Failure: The deviation in expected output during execution due to a fault. These are stages from coding mistake to
observable issue.

9) Define Regression Testing:

Regression Testing is done to ensure that new changes haven’t affected the existing functionality. It is repeated testing of an
already tested program after modifications. It’s critical during software maintenance and after bug fixes or feature updates.

10) What is a Test Case Design?

Test case design is the process of creating inputs, actions, and expected results to verify software functionality. It helps in
systematic testing and better coverage. Good test cases are clear, reusable, and traceable to requirements.
11)Explain Software Testing Life Cycle (STLC)
STLC is a structured process followed during software testing to ensure the quality of the product. It consists of several phases,
each with specific goals and deliverables.

Phases of STLC:
1. Requirement Analysis
o QA team studies and understands the testing requirements.
o Identifies testable features and potential testing types needed.
2. Test Planning
o Creates the test plan and strategy.
o Defines scope, objectives, resources, schedule, and tools.
3. Test Case Design/Development
o Test cases and test data are created based on requirements.
o Review and approval of test cases are done.
4. Test Environment Setup
o Prepares hardware and software conditions for testing.
o Ensures the environment mimics the production system.
5. Test Execution
o Testers run the test cases and record the results.
o Defects are reported and tracked.
6. Test Cycle Closure
o Evaluates test completion criteria.
o Prepares test summary report and metrics.

12) Difference between Alpha and Beta Testing:

15) Stub and Driver in Unit Testing:

Stub:
 A stub is a dummy program that simulates the behavior of lower-level modules that are not yet developed.
 Used in top-down integration testing.
 Example: If function A calls B, but B isn’t ready, a stub for B returns hardcoded or expected output.
Driver:
-A driver is a dummy program that calls and tests a lower-level module when the calling module is not ready.
-Used in bottom-up integration testing.
14) Difference between Static and Dynamic Testing:

13) Explain GUI Testing in Detail:

->GUI Testing (Graphical User Interface Testing) is the process of testing the interface of an application to ensure it meets design
specifications and provides a good user experience.
To verify that the visual elements like buttons, menus, text boxes, icons, and other interface components work correctly and
appear as intended.

16) Explain Integration Testing with Its Types:

Integration Testing is the process of testing the interaction between two or more modules to ensure they work together as
expected. It is performed after unit testing and before system testing. To detect interface defects such as data transfer issues,
mismatches in APIs, or communication failures between modules.
Big Bang Integration Testing
 All modules are integrated and tested at once.
 Simple but hard to debug due to poor fault isolation.
Top-Down Integration Testing
 Testing starts from the top module and moves downward.
 Stubs are used to simulate lower modules.

17)Explain Capability Maturity Model (CMM):

-> Capability Maturity Model (CMM) is a framework developed by SEI (Software Engineering Institute) to assess and improve
software development processes in an organization. It defines 5 levels of process maturity, helping organizations improve
quality and efficiency over time.
Level 1 – Initial
 Processes are ad hoc and chaotic.
 Success depends on individual efforts.
Level 2 – Repeatable
 Basic project management processes exist.
 Projects can be repeated with similar success.
Level 3 – Defined
 Processes are well-documented and standardized across the organization.
Level 4 – Managed
 Processes are measured and controlled.
 Data is used to manage quality.
Level 5 – Optimizing
 Focus on continuous process improvement.
18)Explain Testing Principles in Detail
-> 1. Testing Shows the Presence of Defects
Testing can reveal bugs, but it cannot prove that the software is completely error-free.
2. Exhaustive Testing is Impossible
It's not practical to test all inputs and scenarios. Instead, focus on risk-based and prioritized testing.
3. Early Testing Saves Time and Cost
The sooner defects are found (e.g., during requirements/design), the cheaper they are to fix.
4. Defect Clustering
Most defects are found in a small number of modules (Pareto principle – 80/20 rule).
5. Pesticide Paradox
Repeating the same tests will no longer find new bugs. Test cases need regular updates and improvements.
6. Testing is Context Dependent
Different types of software require different testing strategies (e.g., web app vs embedded system).
7. Absence-of-Errors Fallacy
Even if the software is bug-free, it’s useless if it doesn’t meet the user’s needs or requirements.

19) Cyclomatic Complexity of a Code That Accepts 3 Integers and Prints Highest and Lowest
Cyclomatic Complexity (CC) is calculated using the formula:
CC = E - N + 2P
Where:
 E = number of edges
 N = number of nodes
 P = number of connected components (usually 1 for a single program)

20)Difference between Quality Assurance (QA) and Quality Control (QC)

22) Testing for Real-Time Systems

Real-Time Systems (RTS) have strict timing constraints. Testing for these systems ensures that they meet both functional and
timing requirements. Key aspects include:
 Timing Constraints: Testing how the system responds within defined time frames.
 Concurrency: Ensuring correct behavior in multi-threaded or multi-tasking environments.
 Stress and Load Testing: To check system performance under heavy load or unusual conditions.
 Deterministic Behavior: Verifying that the system performs predictably under all conditions.
23) Statement Coverage Criteria of White-Box Testing
Statement Coverage (or Line Coverage) is a white-box testing metric that ensures every line of code in a program is executed
at least once during testing.
Goal: To identify code that has not been tested by covering all possible statements.
Formula:
Statement Coverage = (Number of executed statements / Total statements) * 100

24) Explain CMM in Detail

The Capability Maturity Model (CMM) is a framework for improving software development processes. It defines five maturity
levels:
1. Initial: Processes are unpredictable and chaotic.
2. Repeatable: Basic project management processes are established.
3. Defined: Processes are standardized across the organization.
4. Managed: Metrics and data are used to control processes.
5. Optimizing: Continuous process improvement through feedback and innovation.
CMM helps organizations systematically improve their software processes, ensuring higher quality and predictable project
outcomes.

25) Software Review

Software Review is a process of evaluating software to find defects or improvement areas, typically through peer review.
Types:
 Formal Inspection: Structured and planned review, often with checklists.
 Walkthroughs: Informal discussions and code walkthroughs with the development team.
 Peer Reviews: Developers reviewing each other’s work for improvements or errors. Reviews focus on detecting
defects early, improving the software’s quality.

26) Goal Question-Metric (GQM) Model

The GQM model helps structure the measurement process for software quality. It involves three stages:
1. Goal: Define the goal of the measurement (e.g., improve code quality).
2. Question: Formulate questions to achieve the goal (e.g., How many defects were reported?).
3. Metric: Define the metrics or data to collect (e.g., defect density, defect type). This approach ensures that metrics
collected are aligned with business goals.

27) Load Runner

LoadRunner is a performance testing tool from Micro Focus. It is used to simulate virtual users and measure the behavior of
the application under heavy load.
Key Features:
 Virtual User Generation: Simulates multiple users interacting with the system.
 Performance Monitoring: Measures response times, resource usage, and system behavior under load.
 Scripting: Allows you to script user behavior and automate the test.

28) Rational Robot

Rational Robot is an automated testing tool for functional and regression testing of applications. It is part of IBM’s Rational
suite.
Key Features:
 Test Automation: Enables automated functional testing for GUI applications.
 Scripting: Uses scripting languages for advanced testing scenarios.
 Integration: Integrates with other Rational tools for comprehensive test management.