[go: up one dir, main page]

0% found this document useful (0 votes)
50 views8 pages

Software Testing Levels Explained

Software testing notes
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
50 views8 pages

Software Testing Levels Explained

Software testing notes
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 8

Software Testing

Assignment No.3
Ch 3.Levels of Testing

Q.1.State True or False:


1. The purpose of levels of testing is to make software testing systematic and easily
identify all possible test cases at a particular level.
True - The purpose of levels of testing is to make software testing systematic and
easily identify all possible test cases at a particular level.

2. Unit testing is performed to test the individual units of software.


True - Unit testing is performed to test the individual units of software.

3. The goal of load testing is to improve performance bottlenecks and to ensure


stability and smooth functioning of software application before deployment.
True - The goal of load testing is to improve performance bottlenecks and ensure
stability and smooth functioning of the software application before deployment.

4. Testing strategy also decides test cases, test specifications, test case decisions, and
puts them together for execution.
False - While testing strategy guides the overall testing approach, it does not decide
individual test cases or specifications. Those are determined during the test planning
and design phases.
5. In top-up integration testing each module at lower levels is tested with higher
modules until all modules are tested.
False - In top-down integration testing, each module at higher levels is tested with
lower modules until all modules are tested.

6. The integration testing is aimed at ensuring that all the modules work properly as
per the user requirements when they are put together (that is, integrated).
True - Integration testing ensures that all the modules work properly as per the user
requirements when they are put together.

7. Performance testing measures the quality attributes of the system, such as


scalability, reliability and resource usage under various workload.
True - Performance testing measures the quality attributes of the system, such as
scalability, reliability, and resource usage under various workloads.

8. Validation testing focuses on the testing of software against the requirements


specified by the customer.
True - Validation testing focuses on testing software against the requirements
specified by the customer.

9. Unit testing is used to verify the code produced during software coding and is
responsible for assessing the correctness of a particular unit of source code.
True - Unit testing is used to verify the code produced during software coding and is
responsible for assessing the correctness of a particular unit of source code.
Q.2.Short Answer Questions.
1. What software testing strategy?
Software testing strategy is a high-level plan that outlines the testing approach,
objectives, resources, and schedule for a testing process. It defines the scope
and methods to be used, ensuring systematic and effective testing.
2. List levels for testing.
Common levels for testing include:
 Unit Testing
 Integration Testing
 System Testing
 Acceptance Testing
3. What is the purpose of load testing?
The purpose of load testing is to assess how a system or software application
behaves under expected or peak load conditions. It helps identify performance
bottlenecks, ensures stability, and verifies that the software can handle the
expected number of users or transactions.

4. Define acceptance testing?


Acceptance testing is the phase of testing where the software is evaluated to
ensure that it meets the specified requirements and is ready for deployment. It is
often performed by end-users or stakeholders.

5. Compare alpha and beta testing any two points.


Alpha Testing:
 Conducted by the internal development team.
 Takes place before the software is released to external users.

Beta Testing:
 Conducted by a select group of external users.
 Takes place after alpha testing and before the final release.
6. Define security testing.
Security testing is a type of testing that focuses on identifying vulnerabilities and
weaknesses in a software application's security. It aims to ensure that the system
is resistant to unauthorized access, attacks, and protects data integrity.

7. What is the purpose of usability testing?


Usability testing aims to evaluate how user-friendly and easy to use a software
application is. It helps identify user interface issues, navigation problems, and
overall user experience.

8. Define compatibility testing?


Compatibility testing is the process of evaluating a software application's
compatibility with different operating systems, browsers, databases, and
hardware. It ensures that the software functions correctly across various
environments.

9. Give the purpose of accessibility testing.


Accessibility testing ensures that a software application is usable by people with
disabilities. The purpose is to identify and rectify any barriers that might hinder
access for individuals with visual, auditory, motor, or cognitive impairments.
Q.3.Long Answer Questions.
1. What is meant by testing levels? Explain with the example.
Definition:
Testing levels refer to the stages in the software development life cycle where
testing is performed. Each level has specific objectives, focuses, and is
designed to catch different types of defects.

Example:

Unit Testing: This is the first level of testing where individual components or
modules are tested in isolation. For example, in a banking application, a unit
test might involve checking the correctness of a function that calculates
interest.

Integration Testing: In this level, the interaction between different modules is


tested. For instance, testing the communication between the user interface
and the database in the banking application.

System Testing: The entire system is tested to ensure that it meets the
specified requirements. In the banking application, this might involve testing
end-to-end transactions and interactions.

Acceptance Testing: This level involves testing to ensure that the software
meets the user's expectations. For the banking application, acceptance testing
might involve users validating that all expected features work as intended.

2. Write a short note on: A strategic approach to software testing.


A strategic approach to software testing involves planning and implementing a
testing process that aligns with the overall goals and objectives of the
software development project. It includes defining the scope, objectives,
resources, and methods to ensure effective testing. A well-defined testing
strategy contributes to delivering a high-quality software product, reducing
risks, and ensuring that the software meets user expectations.
3. What is unit testing? How it works? Also state its advantages and
disadvantages.
Definition:
Unit testing is the process of testing individual units or components of a
software application in isolation to ensure their correctness.

How it works:
Developers write test cases for individual functions or methods, and these
tests are executed to verify that the code behaves as expected.

Advantages:
 It helps identify and fix bugs early in the development process.
 Facilitates better code maintainability and modularity.
 Provides a foundation for automated testing.
Disadvantages:
 It may not catch integration issues between units.
 Time-consuming when dealing with complex systems.
4. What is alpha and beta testing? Differentiate between them. Any four
points.
Alpha Testing:
Conducted by the internal development team.
Takes place before the software is released to external users.
Beta Testing:
Conducted by a select group of external users.
Takes place after alpha testing and before the final release.

5. What is system testing? How it test the system? Also list its different types.
Definition:
System testing involves testing the entire system as a whole to ensure that it
meets specified requirements.

How it works:
Test cases cover end-to-end scenarios, checking that all components work
together seamlessly.

Types:
Functional Testing: Verifies that the system functions according to
specifications.
Performance Testing: Assess system responsiveness, speed, and scalability.
Security Testing: Ensures the system is resistant to unauthorized access.
6. Describe configuration testing with the help of example.
Configuration testing is the process of testing the system with each one of the
supported software and hardware configurations.
• The execution area supports configuration testing by allowing reuse of the
created tests. Configuration testing is the process of checking the operation of
the software we are testing with various types of hardware.
• Configuration testing is the process of testing the system with each one of
the supported software and hardware configurations.
Example:
Verifying that a web application functions correctly on different browsers like
Chrome, Firefox, and Safari.
7. What is stress testing? Describe its process diagrammatically.
Stress testing is a software testing technique designed to determine the
behavior of the software under abnormal situations.

The stress testing process will be completed into the following steps:
Step 1: Detect the Testing Environment: In this step, we will identify the
network, software, and hardware configurations and tools available to achieve
the stress test.

Step 2: Find Performance Acceptance Criteria: In this step, we will find the
performance acceptance criteria, which help us categorize the metrics used to
test the application's performance under stress.

Step 3: Plan and Design Stress Tests: In this step, we will plan and design a
stress test plan, identify test scenarios etc.

Step 4: Configure the Test Environment: In this step, we will move to next step
where we create the test environment, tools and resources essential to
perform each approach as features and components become available for
test.
Step 5: Implement Test Design: In this step, we will develop the stress tests
resulting the test design best performs.
Step 6: Execute Tests: In this step, we will execute the particular test, observe
and confirm the tests along with test data and output collection.
Step 7: Analyze the Results: In this step, we will analyze the outcomes,
combine and share the respective teams' output data.

8. What is regression testing? State its advantages and disadvantages.


Regression Testing: The regression testing is a type of software testing that
confirms that a recent program or code change did not affect existing
functionality. It also ensures that over time no old errors occur by adding new
software modules.
Advantages of Regression Testing:
 Regression testing ensures the software is working very well even after
introducing many changes and modifications.
 The regression testing ensures that the unchanged parts of software
system work properly according to specification.
 This testing ensures that all errors that have occurred in software
system due to modifications are corrected and do not further affect
the working of the software.
Disadvantages of Regression Testing:
 The regression testing requires knowledge about the software system
and how it affects by the existing functionalities.
 Regression testing is time-consuming and expensive activity.
9. What is usability testing? Explain its process diagrammatically.
Usability testing is a software testing technique used in user-centered
interaction design to evaluate a software product by testing it on users.

Steps in usability testing are explained below:


Step 1: Planning: In this step, the team makes the test plan and generates
some document samples that help the testing team complete the usability
testing tasks.
Step 2: Team Recruiting: In this step, we will move to the next step of usability
testing, which team is recruiting. As the name suggests itself, here we will hire
or recruit the end-user delegates and the participants or the test engineers as
per the budget and density of the product.
Step 3: Test Execution: In the test execution step, the test engineers execute
the usability testing and implement their assigned responsibilities.
Step 4: Test Result Documentation: The test result documentation step
includes the results based on the test execution step and then proceeds for
further analysis.
Step 5: Data Analysis: In this step, the response or the feedback is obtained
from usability testing evaluation in the data analysis phase. And the outcomes
are classified and the patterns are acknowledged.

Step 6: Reporting: After performing all the above steps successfully, we will
finally reach the last step of the usability testing process is reporting.

You might also like