UNIT 2

1. What is integration testing? Explain its various types.

Ans:
● Integration testing is like making sure all the different parts of a computer
program talk to each other nicely
● Imagine a team building a video game: one person is in charge of the
characters, another does the background, and a third handles the sound.
● Integration testing is when they check if the characters move smoothly in
the background and if the sound matches the actions.
● It's like making sure all the pieces of the game fit together properly.
● It's like the step in between where they ensure everything works well
together before presenting the final game.
● Various Types of Integration Testing:
1. Bottom-Up Integration Testing:
a. Testing begins with the lower-level modules, progressively
integrating higher-level modules.
b. Advantages: Early testing of basic functionalities, easier to
identify and fix lower-level issues.
c. Disadvantages: May require the use of drivers to simulate
higher-level modules
2. Top-Down Integration Testing:
a. Testing starts from the top-level modules, progressively
integrating lower-level modules.
b. Advantages: Early testing of major functionalities, easier to
identify and fix critical issues.
c. Disadvantages: Stubbing or simulating lower-level modules
may be required

2. Write a short note on system testing.

Ans:
● System testing is the stage where the entire software system is examined as
a complete and integrated entity
● It's the moment of truth, where the system faces rigorous scrutiny to make
sure it meets specified requirements and works seamlessly.
● This testing phase looks closely at the overall functionality, performance,
and reliability of the software.
● It's not just about checking if individual parts work; it's about making sure
they work together like a well-choreographed dance.
● From user interfaces to handling data, system testing covers a wide range
of things, leaving nothing unchecked.
 ● The goal is simple but crucial: find any differences between what's
expected and what actually happens.
● In addition, system testing involves stress-testing the software under
extreme conditions to ensure it can handle unexpected loads and still
perform effectively.
● Compatibility with various operating systems, devices, and browsers is also
assessed to guarantee a smooth user experience across different
environments.

3. Design test case for login page

Ans:
● Test Suite ID: TS002
● Test Case ID: TC002
● Test Case Description: To verify successful login functionality on the login
page
● Relative Requirement: RS002
● Pre-requisites:
1. Web application is accessible.
2. Valid user credentials (username and password) are available.
● Test Procedure:
1. Navigate to the login page.
2. Enter a valid username and password.
3. Click the "Login" button.
● Test Data:
1. Valid username: sampleuser
2. Valid password: SamplePass123
● Expected Result:
1. Users should be redirected to the home/dashboard page.
2. User's name or profile information should be displayed.
● Actual Result:
1. If the credentials are valid, the result is as expected.
● Status: Pass
● Remark: This is a basic test to ensure that users can successfully log in.
● Created By: Aryan Patil
● Date of Creation: 01/11/2023
● Executed By: Bhupendra Jogi
● Date of Execution: 01/12/2023
 4. What is validation testing?
Ans:
● Validation testing is like the quality check at the end of a production
line—ensuring that the final product meets the intended specifications and
satisfies the user's needs.
● Validation Testing - Workflow:

● The primary focus of validation testing is to ensure that the software meets
the user's expectations and functions as intended in the real-world
environment.
● Essentially, validation testing answers the question: "Does the software do
what it's supposed to do for the user?"
● This type of testing often involves customer or user participation to gather
feedback and verify that the software aligns with their expectations.
● In a nutshell, validation testing is the final check to make sure the software
is not just technically sound but is also a practical and effective solution for
the end user.

5. Difference between alpha beta testing.

Ans:
Alpha Testing Beta Testing

Alpha testing involves both the white Beta testing commonly uses black-box
box and black box testing. testing.

Alpha testing is performed at the Beta testing is performed at the

developer’s site. end-user of the product.

Reliability and security testing are not Reliability, security and robustness are
checked in alpha testing. checked during beta testing.

Alpha testing requires a testing Beta testing doesn’t require a testing

environment or a lab. environment or lab.

Alpha testing may require a long Beta testing requires only a few weeks
execution cycle. of execution.

Multiple test cycles are organized in Only one or two test cycles are there in
alpha testing. beta testing.

Limited to in-house developers and Involves external users who are not
testers. part of the development team.

It is not open to the market and public. It is open to the market and public.

It is used for software applications and It is used for software products.

projects.

6. Define software metrics and its importance, types

Ans:
● Software Metrics helps us understand and keep track of different aspects of
the software, like how big it is or how many issues it has.
● Importance of Software Metrics:
1. Quality Assurance:
They do this by looking at things like problems in the code, how
complicated the code is, and how much of the software is tested.
2. Project Management:
Metrics aid in project planning, tracking progress, and managing
resources effectively.
3. Risk Management:
Metrics help identify potential risks early in the development
process, allowing teams to immediately take proper action before
they grow rapidly.
4. Communication:
Software Metrics make it simple for everyone to understand what's
going on with the project and what the goals are.
● Types of Software Metrics:
1. Source code metrics:
a. Source code metrics are like measurements that tell us about
the quality and characteristics of the code.
 b. They help us understand things like code size, complexity, and
the presence of any issues or bugs.
2. Development metrics
a. Development metrics are like tools that measure how well the
development team is doing.
b. These metrics might include factors like the amount of work
completed, time taken for tasks, and overall team efficiency.
3. Testing metrics
a. Testing metrics are like measurements that focus on how well
the testing process is going.
b. These metrics assess aspects such as test coverage, the number
of defects found, and the overall effectiveness of the testing
efforts.

7. Explain top-down integration testing.

Ans:
● Testing starts from the top-level modules, progressively integrating
lower-level modules.

● In the top-down integration testing, if breadth-first approach is adopted,

then we will integrate module M1 first, then M2, M6. Then we will integrate
modules M3, M4, M5, and at last M7.
● In these, high-level modules are tested first, and then low-level modules are
tested.
● Then, finally, integration is done to ensure that the system is working
properly.
● Stubs and drivers are used to carry out this project.
● This technique is used to encourage or boost the performance of parts that
haven't been combined into a lower level yet.
● Advantages: Interface errors are identified at an early stage and fault
localization is also easier.
● Disadvantages: It requires a lot of stubs and mock objects.
 8. Discuss levels of testing.
Ans:
● Testing Levels of testing refer to the different stages or layers of testing that
are performed on a software system or application.
● Here are the main levels:

● Unit Testing:
1. Verify that each part (unit) of the software functions correctly on its
own.
2. Developers typically perform unit testing, checking code snippets or
small functionalities.
● Integration Testing:
1. Ensure that units work together as expected when combined.
2. Testers verify the communication and collaboration between
different units.
● System Testing:
1. Validate the entire system's functionality, performance, and
behavior.
2. Assess the system as a whole to identify any issues that might arise
from the interaction of components.
● Acceptance Testing:
1. Confirm that the software meets user requirements and is ready for
deployment.
2. End-users or stakeholders participate to ensure the software aligns
with their expectations.
 9. Differentiate between white box and black box testing ?
Ans:
black box white box

It is a way of software testing in which It is a way of testing the software in

the internal structure or the program which the tester has knowledge about
or the code is hidden and nothing is the internal structure or the code or
known about it. the program of the software.

Implementation of code is not needed Code implementation is necessary for

for black box testing. white box testing.

It is mostly done by software testers. It is mostly done by software

developers.

It is a functional test of the software. It is a structural test of the software.

No knowledge of programming is It is mandatory to have knowledge of

required programming

It is also called closed testing. It is also called clear box testing.

It is the least time consuming. It is most time consuming.

It is not suitable or preferred for It is suitable for algorithm testing.

algorithm testing.

Example: Search something on google Example: By input to check and verify

by using keywords loops

Types of Black Box Testing: Types of White Box Testing:

● Functional Testing ● Path Testing
● Non-functional testing ● Loop Testing
● Regression Testing ● Condition testing

10.Write in brief about test case design with an example.

Ans:
● To test software the software testing provides a particular format called a
Test Case.
● A test case is a defined format for software testing required to check if a
particular application/software is working or not.
● A test case consists of a certain set of conditions that need to be checked to
test an application or software
● Below is the table that shows the basic template of a test case:
1. Test suite ID: The ID of the test suit to which this test case belongs
 2. Test Case ID: Each test case should have a unique ID.
3. Test Case Description: Each test case should have a proper
description to let testers know what the test case is about.
4. Relative Requirement: The ID of requirement this test case relates or
faces to
5. Pre requisites: Any pre conditions that must be fulfilled prior to
executing the test
6. Test procedure: step by step procedure to execute the test
7. Test data: Test data could be used as input for the test cases.
8. Expected Result: The result expected after executing the test cases.
9. Actual Result: The result which system shows once the test case was
executed.
10.Status: Set status as Pass or Fail on the expected result against the
actual result.
11.Remark: Comment after execution of test case
12.Created By: Name of the tester who created the test cases.
13.Date of Creation: Date of creation of test cases.
14.Executed By: Name of the tester who executed the test case.
15.Date of Execution: Date when the test cases were executed.
● Example: QUE 3

11.What are the elements of software reliability state factors affecting it ?

Ans:
● There are several factors that contribute to the reliability of software.
● Here are some key elements and factors:
1. Reliability :
a. Reliability refers to the ability of the software to perform its
function consistently and without failure over a specified
period of time.
b. Factors influencing reliability include:
● Proper handling of errors, exceptions, and failures
● Effective error recovery and fault tolerance mechanisms
● Availability of backup and redundancy measures
2. Availability :
a. Availability refers to the readiness and accessibility of the
software for use whenever needed.
b. Factors influencing availability include:
● efficient system and network infrastructure
● Proper handling of system downtime or maintenance
● Quick recovery from failures
 3. Maintainability :
a. Maintainability refers to the ease and effectiveness of
maintaining and updating the software throughout its
lifecycle.
b. Factors influencing maintainability include:
● Modular and well-structured design
● Clear and comprehensive documentation
● Use of coding standards and best practices
4. Testability :
a. Testability refers to the ease with which the software can be
tested to ensure its quality and reliability.
b. Factors influencing testability include:
● Availability of proper testing tools and frameworks
● The design and execution of test cases.
● The effectiveness of quality control processes.
5. Correctness :
a. The correctness of the software refers to its ability to produce
the expected results and perform its intended functions
accurately
b. Factors influencing correctness include:
● Accuracy of requirements analysis and specification
● Quality of the software design
● Accuracy of coding and implementation

12.How to measure quality cost?

Ans:
● Measuring the cost of quality involves assessing various aspects of a
product or service to ensure it meets certain standards.
● Here's a simplified breakdown:
1. Prevention Costs:
a. These are the costs incurred to prevent defects or issues before
they happen.
b. Measure this by looking at expenses for training, quality
planning, and process improvement.
2. Appraisal Costs:
a. This involves evaluating and checking the product or service
to ensure it meets the specified quality standards.
b. Measure by assessing expenses related to inspections, testing,
and quality audits.
3. Internal Failure Costs:
 a. These are the costs incurred when defects are identified
before the product or service reaches the customer.
b. Measure by looking at expenses for rework, scrap, and dealing
with customer complaints.
4. External Failure Costs:
a. These occur when defects are identified by the customer after
the product or service has been delivered.
b. Measure by considering costs related to warranty claims,
product returns, and customer support.
● Ideally, a well-balanced approach minimizes failure costs by investing
appropriately in prevention and appraisal activities.

13.Write a short note on SQA plan?

Ans:
● Software Quality Assurance (SQA) is simply a way to assure quality in the
software.
● It focuses on improving the process of development of software so that
problems can be prevented before they become a major issue.
● The documentation section of the SQA plan describes each of the work
products produced during the software process.
● The documentation section consists of:
1. Project documents such as project plan requirements document, test
cases, reports, user manual, and administrative manuals.
2. Models such as ERDs, class hierarchical.
3. Technical documents such as specifications, test plans.
4. User documents such as help files.
● Example:
1. Project Documents:
a. Requirements Document:
Lists what the website needs to do, like user accounts and
secure payments.
b. Test Cases:
Scenarios to ensure the website works correctly, e.g., testing
the shopping cart.
c. Reports:
Regular updates on project progress, development, testing, and
issues.
2. Models:
a. ERDs:
 Visual representation of how entities (users, books, orders) are
related.
b. Class Hierarchical Models:
Illustrates hierarchy and relationships among classes, e.g.,
categorizing books.
3. Technical Documents:
a. Specifications:
Details the technical aspects of the website for developers.
b. Test Plans:
Outlines the approach to testing the website's functionalities.
4. User Documents:
c. Help Files:
Assists users with common issues on the website, like
forgotten passwords.

14.Explain any 5 guidelines for formal technical review (FTR)

Ans:
● Following are set of guidelines for FTR
1. Take Written Notes:
a. During the Formal Technical Review (FTR), participants should
actively take written notes.
b. This practice ensures that all feedback, identified issues, and
suggestions are documented in real-time.
2. Set an Agenda and Maintain It:
a. Before the review session, establish a clear agenda outlining
the topics to be covered and the allotted time for each.
b. Stick to the agenda during the review to maintain focus and
efficiency.
3. Limit Debate and Contradiction:
a. Encourage a constructive and time-efficient discussion by
limiting unnecessary debates and contradictions.
b. Setting a time limit for discussions on specific points helps
maintain a balance between thorough examination and time
management
4. Review Your Early Reviews:
a. Continuously improve the review process by periodically
reviewing and reflecting on past review sessions.
b. Learning from experience enhances the efficiency and quality
of future reviews.
5. Review the Product, Not the Producer:
 a. Emphasize that the focus of the review is on the product or
work being examined, not on the individual who created it.
b. Avoid personal critiques or attributing issues to specific team
members.

15.Explain bottom up integration testing?

Ans:
● Bottom-up testing is like building a tower block by block, starting from the
bottom and moving upwards. It involves combining and testing small parts
of the software first and gradually adding more until the whole system is
tested.
● In these, low-level modules are tested first, and then high-level modules are
tested.
● Bottom-up testing is user-friendly testing and results in an increase in
overall software development.
● This testing results in high success rates with long-lasting results.
● Diagram:

● In the last, modules or components are combined together to form cluster 1

and cluster 2. After this, each cluster is tested with the help of a control
program.
● Advantages : It is easy and simple to create and develop test conditions.
● Disadvantages : Towards the top of the Hierarchy, it becomes very
complicated.
 16.Write a short note on unit testing?
Ans:
● Unit testing is a crucial aspect of software testing that concentrates on
assessing individual units or components within a software system.
● The primary aim is to confirm the accuracy and proper functioning of each
unit, ensuring it aligns with its intended purpose.
● Here are some key aspects to understand:
1. Scope:
a. Unit testing zeroes in on the smallest testable parts of the
software, like functions, methods, or classes.
2. Purpose:
a. The core purpose of unit testing is to validate that each unit of
code operates correctly and fulfills its specified requirements.
3. Independence:
a. It is essential for unit tests to be independent, meaning the
outcome of one test should not impact the results of another.
4. Test Cases:
a. Unit tests are constructed based on test cases outlining the
expected behavior of the code.
5. Test Automation:
a. To enhance efficiency and repeatability, unit tests are
commonly automated.
6. Continuous Integration:
a. Unit testing is seamlessly integrated into the development
workflow as part of continuous integration (CI).

17.What is smoke testing? What are the benefits of smoke testing?

Ans:
● Smoke testing is like a quick check to see if the basic functionalities of the
software are working fine.
● It's done early in the testing process, often right after a new build or
version is deployed.
● Benefits of Smoke Testing:
1. Early Detection of Major Issues:
It helps find important issues quickly, so we can fix them before
doing more detailed testing.
2. Time and Cost Efficiency:
Since smoke testing is fast, it saves time and resources by spotting big
issues without doing a lot of detailed testing.
3. Risk Mitigation:
 By finding major problems early, it lowers the risk of spending time
on detailed testing when the basic parts of the software are not
working well.
4. Build Verification:
It's like making sure the latest version of the software is stable before
doing more testing.
5. Efficient Workflow:
Smoke testing helps keep the workflow smooth by stopping bad
versions from going to the next testing step.

18.Write a short note on Black box testing?

Ans:

● It focuses on validating that the software behaves as expected from the

user's perspective.
● Testers input specific inputs into the system and observe the corresponding
outputs, checking if the results align with the defined requirements.
● Black box testing is versatile, covering various testing levels such as unit
testing, integration testing, system testing, and acceptance testing
● It ensures that the software meets specified requirements, identifies
functional defects, and guarantees a positive user experience.
● In summary, black box testing is like exploring the outer shell of a
product—evaluating its functions without knowing the complex details of
its construction.
● This approach is crucial for validating that the software meets user
expectations and performs as intended.
 19.What is software testing? Explain testing principles.
Ans:
● Software testing is a procedure of implementing software or the
application to identify the defects or bugs.
● Here, in this section, we are going to learn about the seven essential
principles of software testing.
1. Testing shows the presence of defects
The primary purpose of doing testing is to identify the numbers of
unknown bugs with the help of various methods and testing
techniques
2. Exhaustive Testing is not possible
testing focuses on the most critical and likely areas where defects
may exist.
3. Early Testing
Early testing helps catch defects in the early stages when they are
less costly to fix.
4. Defect Clustering
This principle guides testers to concentrate their efforts where
defects are most likely to be found.
5. Pesticide Paradox
The Pesticide Paradox warns against using the same set of tests
repeatedly, as it may not uncover new defects.
6. Testing is context-dependent
Testing strategies and techniques should be adapted based on the
context of the project
7. Absence of errors fallacy
Testing helps identify and reduce the number of defects but cannot
eliminate them entirely.

20.What is Validation testing? Give an example.

Ans:
● Write basic from Q4
● Example:
1. Let's consider a banking application.
2. In validation testing, we would verify that the software accurately
performs financial transactions, calculates interest correctly, and
securely handles user data.
3. The testing would involve scenarios where users transfer money
between accounts, check their balance, and perform other typical
banking operations.
 21.Explain any 5 quality assurance activities.
Ans:
● Let's breakdown into each of these quality assurance activities:
● Process Checklists:
1. Process checklists are like step-by-step to-do lists that teams follow
during software development.
2. The goal of process checklists is to keep things organized and
prevent errors by providing a clear guide for each stage of
development.
● Test Planning:
1. QA is involved in creating test plans that outline the overall testing
strategy, scope, resources, schedule, and activities.
2. Test planning ensures that testing efforts are well-organized,
systematic, and aligned with project objectives.
● Process Standards:
1. Process standards are the rules and guidelines that everyone in the
team follows
2. Process standards exist to create a consistent way of working,
ensuring that everyone understands and follows the same rules
during development.
● Process Documentation:
1. Process documentation is like the instruction manual for software
development.
2. The purpose of process documentation is to provide clear and
structured information, making it easy for everyone to know what
they should be doing and how.
● Project Audit:
1. A project audit is like a thorough check-up for a project.
2. The purpose of a project audit is to review and evaluate the project
to catch any issues, risks, or areas for improvement.

22.Write a short note on quality tools.

Ans:
● There are seven basic quality tools used in organizations.
● These tools can provide much information about problems in the
organization assisting to derive solutions for the same
● Flow Charts:
1. This is one of the basic quality tools that can be used for analyzing a
sequence of events.
 2. Flow charts can be used for any field to illustrate complex processes
in a simple way.

● Histogram:
1. Histogram is used for illustrating the frequency and the extent in the
context of two variables.
2. Histogram is a chart with columns. This represents the distribution
by mean.

● Cause and Effect Diagram:

1. Cause and effect diagrams are used for understanding
organizational or business problem causes.
2. Organizations face problems everyday and it is required to
understand the causes of these problems in order to solve them
effectively.
● Check Sheet:
1. A check sheet can be introduced as the most basic tool for quality.
2. A check sheet is basically used for gathering and organizing data.

● Control Charts:
1. Control chart is the best tool for monitoring the performance of a
process.
2. These types of charts can be used for monitoring any processes
related to the function of the organization.
 ● Pareto Charts:
1. Pareto charts are used for identifying a set of priorities.
2. You can chart any number of issues/variables related to a specific
concern and record the number of occurrences.

23.What are test plans and test cases? Explain with an example
Ans:
● Test already ahe test plan cha and fakt khalcha ahe
● A test plan is like a roadmap for testing—it outlines the overall strategy,
objectives, resources, and schedule for a testing project.
● It details what needs to be tested, how it will be tested, and who will be
involved.
● It details what needs to be tested, how it will be tested, and who will be
involved.
● Example of a Test Plan:
1. Let's say you're testing an e-commerce website.
2. Your test plan might include sections on testing different aspects like
product search functionality, user registration, payment processing,
and security.
 3. It outlines the scope, test environments, testing tools, and
responsibilities of each team member involved in the testing process.

24.Short note on STLC.

Ans:
● Software Testing Life Cycle (STLC) is a process used to test software and
ensure that quality standards are met.
● Tests are carried out systematically over several phases.
● During product development, phases of the STLC may be performed
multiple times until a product is deemed suitable for release.

● Requirements:
Understand and analyze the software requirements to form the foundation
for testing activities.
● Test Planning:
Develop a comprehensive test plan that outlines the testing strategy, scope,
resources, schedule, and deliverables.
● Test Design and Review:
Develop test cases and design testing scenarios based on the identified
requirements.
● Test Cases Preparation:
Prepare test cases that serve as detailed instructions for executing tests.
● Test Execution:
Execute the prepared test cases to validate the functionality of the software
and identify defects.
● Test Report/Bug Report:
Document and communicate the results of testing activities, including
identified defects.
● Bug Fix/Regression Test:
Address and fix reported defects, and ensure that the fixes do not introduce
new issues
● Software Release:
Prepare the software for release to production or the next phase of the
development life cycle.