Software Testing – Unit III & Unit IV (Detailed Notes)
Exam-Oriented Study Material with Theory, Examples & Diagrams
UNIT III – Applying Your Testing Skills
1. Configuration Testing
Configuration Testing is the process of testing a system under different hardware and
software configurations to ensure stability and performance. It helps identify compatibility
and performance issues caused by different environments.
Purpose: To ensure that software works correctly with various operating systems,
browsers, memory sizes, processors, and network environments.
Steps:
1. Identify all supported configurations.
2. Set up the test environment for each configuration.
3. Execute test cases.
4. Record and analyze results.
Example: Testing an application on Windows 10, Windows 11, and macOS systems.
2. Compatibility Testing
This testing ensures that the software works correctly across different environments, such
as OS, browsers, and networks.
Backward Compatibility: Checks that a new version of software works with older
environments or files. (e.g., MS Word 2021 opening Word 2010 files)
Forward Compatibility: Checks that an old version of software can handle new
environment or file formats (e.g., Word 2010 opening Word 2021 files).
Benefits:
- Ensures smooth upgrade process.
- Reduces maintenance costs.
- Improves user satisfaction.
3. Testing Multiple Versions
This testing ensures that multiple releases or versions of the software (v1.0, v1.1, v2.0)
function properly. It helps to verify backward and forward compatibility and detect
regression issues.
4. Data Sharing Compatibility
Verifies that data exchanged between different software versions or systems remains
intact and readable.
Example: Exporting a file from Excel 2016 and opening it in Excel 2021 without loss of
data.
5. User Interface (UI) Testing
UI Testing validates all graphical elements like buttons, menus, forms, and icons to ensure
they function and appear correctly.
Effective UI Testing:
- Checks layout consistency, color contrast, alignment, and readability.
- Ensures navigation and responsiveness.
- Verifies accessibility features.
Testing for Disabled Users:
- Focuses on accessibility testing for visually or physically challenged users.
- Uses screen readers, voice commands, and text alternatives for images.
- Follows WCAG (Web Content Accessibility Guidelines).
UNIT IV – Documentation, Security and Website Testing
1. Documentation Testing
Documentation Testing ensures that all product-related documents (user manuals, help
files, technical guides) are accurate, up-to-date, and match the product’s functionality.
Types of Documentation:
1. User Documentation: Manuals for end-users.
2. System Documentation: Technical details, architecture, and source code info.
3. Process Documentation: SRS, design documents, test plans.
Importance:
- Ensures clarity for users.
- Helps maintenance and support teams.
- Reduces training effort and cost.
2. Security Testing
Security Testing ensures the system protects data and prevents unauthorized access.
Key Concepts:
- Threat Modelling: Identifies possible security threats and designs measures to counter
them.
- Buffer Overrun (Overflow): Occurs when more data is written to a buffer than it can
hold. May lead to system crash or unauthorized access.
- Safe String Functions: Use secure programming functions (like strncpy()) to prevent
overflows.
- Computer Forensics: Investigation and analysis of security incidents to collect digital
evidence and enhance future protection.
3. Web Site Testing
It verifies that websites function correctly, are secure, and display properly across
browsers and devices.
Web Page Fundamentals: Testing the structure, layout, and usability of a webpage.
Black Box Testing: Checks external behavior of web pages – verifying text, links,
images, forms.
Gray Box Testing: Tester has partial knowledge of the system’s internal structure (used
for database and session validation).
White Box Testing: Focuses on internal code, logic, and structure.
Configuration & Compatibility Testing for Websites:
Ensures that the website works on various browsers (Chrome, Edge, Firefox, Safari),
screen sizes, and devices.
Example:
Testing an e-commerce site on mobile and desktop browsers to verify responsiveness and
layout consistency.