Software testing unit 4 notes

Test planning involves defining the scope, objectives, and resources for a
testing effort. It includes creating test strategies, test cases, and schedules to
ensure thorough and effective testing. The goal is to systematically verify and
validate a product to meet quality and performance requirements.
1) Preparing a Test Plan
2) Scope Management
3) Deciding Test Approach
4) Setting up criteria for testing
5) Identifying Responsibilities
6) Staffing
7) Training needs
8) Resource requirements
9) Test Deliverables
10) Testing tasks

IMP
Characteristic Test planning Test execution

Run the test cases that have been

Define the scope, approach, and resources
Goal developed in the test planning
required to test a software application
phase

Test plan, test schedule, test resource

Deliverables Test results, defect reports
estimates, test assignments

Identify the features to be tested, the types of Set up the test environment,
tests to be performed, and the criteria for execute the test cases, and record
Activities success. Create a test schedule, estimate the the results. Report on the test
resources required, and assign tasks to team results and identify any defects
members. found.

Google classroom chapter 3

Scope Management:
Scope management in test planning involves defining the boundaries of what
will be tested. It includes identifying the features or functionalities to be
tested, prioritizing them, and deciding which ones will not be tested. It ensures
a clear understanding of what constitutes a release and helps manage the
scope to align with project goals and resource constraints.
Test Approach:
The test approach outlines the strategy and methodology for conducting
testing. It defines the types of testing to be performed (e.g., functional,
integration, performance), specific test scenarios and configurations, and the
localization and non-functional testing requirements. The test approach guides
how testing will be executed to ensure that all aspects of the software are
thoroughly validated.
Setting Up Criteria for Testing:
Setting up criteria for testing involves defining conditions that determine when
testing should be halted or resumed. For example, criteria may include
stopping testing when a certain number of defects are encountered or when
show-stopper issues prevent further progress. It also considers factors like the
release of new software versions that may affect the testing process.
Identify Responsibility:
Identifying responsibility ensures that clear accountability is assigned for
various testing tasks. It involves specifying who is responsible for what aspects
of the testing process, so team members know their roles and contributions.
This prevents overlapping responsibilities and helps the team work cohesively.
Staffing & Training:
Staffing involves estimating the number of resources required for testing,
considering the effort and time available for a release. It aims to allocate the
right people to the right tasks and prioritize them based on effort, time, and
task importance. Training addresses skill gaps by planning and providing
appropriate training programs to equip team members with the necessary skills
for testing.
Resource Requirements:
Resource requirements cover the hardware, software, and tools needed for
testing. This includes specifying the machine configurations, supporting tools
(like compilers and configuration management tools), software licenses, and
special resources for tasks like load testing or performance testing. Ensuring
the availability of these resources is crucial for successful testing.
Test Deliverables:
Test deliverables encompass the documentation generated during testing. This
includes the test plan itself, various test plans for different aspects of the
project, test case design specifications, actual test cases, test logs generated
during test execution, and test summary reports. These deliverables help
document the testing process, track progress, and communicate results to
stakeholders.
Testing Tasks:
Testing tasks involve estimating the size, effort, and schedule for different
testing activities. This includes tasks such as test execution, scope
management, test approach implementation, criteria setup, responsibility
assignment, staffing, training, resource allocation, and the creation of test
deliverables. Properly planning and managing these tasks is essential for
successful testing projects.
4.2
Configuration testing is a type of software testing that involves testing a
software application under various hardware and software configurations. This
is done to ensure that the software works as expected on a variety of different
systems and to identify any potential compatibility issues.
Configuration testing is important for a number of reasons. First, it helps to
ensure that the software is compatible with a wide range of hardware and
software platforms. This is important because users may be using different
types of computers, operating systems, and browsers. Second, configuration
testing can help to identify any potential performance issues. For example, a
software application may run differently on a computer with a lot of memory
than on a computer with less memory.

Approaching the task

Approaching the task of configuration testing involves a systematic and
organized process to determine what devices to test with and how they should
be tested.
1. Collect Information: Gather information about the hardware and
software requirements of your application. Understand the features and
functionality of your software and how they interact with various
hardware components.
2. Decide Hardware Types: Identify the types of hardware devices that
need to be tested. For example, if your software has printing or sound
features, consider testing printers, sound cards, and other relevant
devices.
3. Select Brands and Models: Determine which hardware brands, models,
and device drivers are relevant for your testing. Focus on devices that are
commonly used or align with the target user base. Consult with sales and
marketing teams or refer to technology magazines for insights. Design
Test Cases: Create detailed test cases for each configuration, specifying
the steps required to conduct the tests. Ensure that the test cases are
clear, repeatable, and document expected outcomes.
4. Execute Tests: Run the test cases on each configuration, carefully logging
and reporting the results. Collaborate with developers and white-box
testers to isolate the source of any issues and differentiate between
software and hardware-related problems.
5. Report and Collaborate: If hardware-related issues are identified, work
with hardware manufacturers to report and resolve these problems. Be
prepared to share test software, test cases, and supporting details to
assist in problem isolation.
4.3
Software compatibility testing means checking that your software
interacts with and shares information correctly with other software. This
interaction could occur between two programs simultaneously running
on the same computer or even on different computers connected
through the Internet thousands of miles apart.
Examples of compatible software are
 Cutting text from a Web page and pasting it into a document
opened in your word processor
 Saving accounting data from one spreadsheet program and then
loading it into a completely different spreadsheet program
Backward compatible and forward compatibility
If something is backward compatible, it will work with previous versions of the
software. If something is forward compatible, it will work with future versions
of the software.

Standards and Guidelines

There are really two levels of these requirements: high-level and low-level
 High-level standards guide the overall compliance, user experience, and
supported features of a software product, focusing on its general goals
and design aspects.
 Low-level standards address technical details like file formats, network
communication protocols, coding conventions, and data structures,
ensuring the software functions correctly and interoperates with other
systems.
 Both high-level and low-level standards are vital for developing and
testing a comprehensive and effective software product.

Data sharing compatibility is a critical aspect of software functionality that

enables seamless exchange of data between applications. It encompasses
various methods and standards to ensure data can be transferred and used
effectively. Here's an explanation of data sharing compatibility using the
provided information:
1. File Save and Load: Saving and loading data to and from disk files is a
common method of data sharing. For compatibility, software must
adhere to low-level standards for disk and file formats, ensuring that
data can be transferred and read by different applications on various
computers.
2. File Export and Import: Many programs support file export and import
to maintain compatibility with older versions and other software. This
involves supporting multiple file formats for importing data. To test
compatibility, you need to create test documents in each compatible
format, ensuring that the importing code correctly converts data to the
new format.
3. Cut, Copy, and Paste: These methods facilitate data sharing in memory
through the Clipboard, allowing users to transfer text, pictures, and
sounds between programs. Compatibility testing ensures that data can
be copied in and out of the Clipboard, considering different data types
and formats.
4. DDE and OLE: Dynamic Data Exchange (DDE) and Object Linking and
Embedding (OLE) are methods for real-time data transfer between
applications. Unlike manual copy and paste operations, DDE and OLE
allow automatic data exchange. Testing ensures that object linking,
embedding, and data exchanging work correctly, enabling features like
automatic updates when underlying data changes, such as in linked
charts.

1. Functionality Testing: This type of testing focuses on verifying that the

web application's features and functions work as intended. Testers check
if all buttons, forms, links, and interactive elements perform their
designated tasks accurately and without errors.
2. Usability Testing: Usability testing evaluates the user-friendliness of a
website. It aims to ensure that the web interface is intuitive, easy to
navigate, and that users can complete tasks efficiently. Feedback is
gathered on the overall user experience.
3. Interface Testing: Interface testing assesses the interactions between
different components of a web application, such as how data is
transferred between the front-end (user interface) and back-end
(server). It ensures seamless communication and data flow.
4. Compatibility Testing: Compatibility testing checks whether a website
functions correctly on various browsers, devices, and operating systems.
It confirms that the web application maintains a consistent user
experience across different platforms.
5. Gray-Box Testing: Gray-box testing combines elements of both black-box
and white-box testing. Testers have limited knowledge of the internal
code but are aware of the system's architecture. It focuses on user
experience, data flow, and specific areas of concern.
6. Performance Testing: Performance testing assesses the web
application's speed, responsiveness, and scalability. It includes load
testing to determine how the site handles increased user traffic, stress
testing to identify performance limits, and other metrics related to speed
and efficiency.
7. Security Testing: Security testing aims to identify vulnerabilities and
weaknesses in a web application. It involves testing for common security
threats like SQL injection, cross-site scripting (XSS), and other potential
risks to protect sensitive data and maintain the website's integrity.