What type of testing had we discussed?

Network Testing tools

Tools used IN BLACK BOX TESTING
• What types of tests are conducted in black-box testing?
Load Testing Tools
• LoadRunner
Simulates real user scenarios and
interactions with an application

• JMeter
An open-source tool that can simulate a
large number of users and requests to
identify performance bottlenecks
 Performance testing tools
• QuickTest Professional (QTP): A
popular choice for functional and
regression tests. Now known as
Unified Functional Testing (UFT).
• Selenium: A popular choice for
functional and regression tests

UFT Selenium

commercial, seat costs free and open source. Anyone can download and modify
as per their testing needs.
Automation Technology Support Selenium can automate only web applications.

UFT can automate almost all the latest technologies,

including Web, Desktop and Mobile Applications. UFT
is also used to automate testing Web Services.
• URL testing tools
URL testing tools are used to evaluate the performance of
websites and web applications. They can be used to
identify issues that affect user experience and site speed
1. ManageEngine OpManager: Tests the
availability of URLs that bring in valuable
traffic
2. Google PageSpeed Insights
Measures website performance for mobile and
desktop, and provides insights into what
affects user experience and site speed
3. Pingdom
• A website monitoring solution that provides tools and
features to analyze the performance and uptime of websites

4. GTmetrix
• A free online tool that tests website speed and allows users to
download their results as a PDF

5. Katalon Studio
• A free tool for test automation that can be used to test
websites, mobile apps, and web apps

6. WebLOAD
• A load testing solution for enterprise-grade web applications
that simulates large-scale user traffic
iPerf command in server
• Iperf can be used with the command " iperf3 "
followed by any flags.
• -s : Specify that the instance is to act as the server node.
• -c : Specify that the instance is to act as the client node
connecting to a given server.
• -p : The port number to listen/connect to.
Ex. iperf -s
iPerf command in client

Run iPerf in client mode, connecting to an

-c, --client host
iPerf server running on host.

Use SCTP rather than TCP (Linux, FreeBSD

--sctp
and Solaris). (new in iPerf 3.1)

-u, --udp Use UDP rather than TCP

The --sctp command-line
option in iperf is used to test
network performance over the
SCTP (Stream Control
Transmission Protocol)
instead of the default TCP or
UDP protocols. Here's how to
use it:
In iperf, the -c option is used to run the tool in client mode, where it connects to a
specified server and performs a network performance test. Here's how to use it
effectively:
Use UDP rather than TCP
• What key areas should be tested for compatibility when
evaluating a web application?

• What key areas should be tested for compatibility when

evaluating OS or different versions of Windows (e.g., Windows
10, Windows 11)macOS (e.g., macOS Monterey, macOS
Ventura)Linux (e.g., Ubuntu, CentOS)Mobile OS (e.g., Android
12, iOS 15)?

• What key areas should be tested for compatibility when

evaluating network environment?
Network environment
Example are the type of network (identify goal wireless or wired?) what
type of network environment do you plan to establish?
Identify a compatible network media for your plan
Test
• Wi-Fi (different router types, speeds, and standards like Wi-Fi 5 and
Wi-Fi 6)
• Ethernet (standard wired connections with different bandwidths, type
of ethernet cable)
• Mobile Data (e.g., 4G, 5G, or slower 3G connections)
Steps For System Compatibility Testing
A. Requirement Analysis: Understand the target environments,
platforms, and configurations.
B. Test Planning: Define the scope, tools, and test cases to cover all
compatibility scenarios.
C. Environment Setup: Create or simulate different environments
using physical devices
D. Re-testing and Regression Testing: Re-test to ensure fixes
work and no new issues are introduced.
Sample procedure and documentation steps in compatibility testing

Scenario: Testing System Compatibility for a Web Application Across

Different OS Versions (Windows 10 vs. Windows 11)

A. Analysis:
The goal is to ensure that the web application functions seamlessly
across different versions of the Windows OS (Windows 10 and
Windows 11). This includes checking that features, performance, UI,
and system resources behave consistently across both versions. The
analysis phase will identify potential compatibility risks, such as
variations in OS-specific browser behavior or UI rendering issues.
B. Test Planning:
[Link]:
Verify that the web application functions properly on Windows 10 and
Windows 11. Focus on compatibility for UI elements, browser
behavior, and system resource usage.
[Link]:
• Browser Compatibility: Test on browsers like Chrome, Firefox, and Edge on
both OS versions.
• Performance: Measure the app's resource usage (CPU, memory) on both OS
versions.
• UI Rendering: Ensure that all UI elements appear correctly and scale properly
across screen sizes.
3. Test Cases:
• Test the UI responsiveness and appearance (buttons, images, menus).
• Validate login/logout functionality across browsers.
• Measure application load time and resource consumption on both OS
versions.
• Check for any security settings that may block the app on one OS but
not the other.
C. Environment Setup:
[Link] Systems:
1. Set up test environments for Windows 10 and Windows 11. Ensure both OS versions are
up-to-date with the latest security patches.
[Link]:
1. Install the latest versions of Chrome, Firefox, and Edge on both OS versions for testing.
[Link] Resources:
1. Set up performance monitoring tools (e.g., Task Manager on Windows) to track CPU, RAM,
and disk usage during testing.
[Link] Tools:
1. Use Selenium for automated UI testing.
2. Use JMeter to test application load times and performance metrics.
[Link] Setup:
1. Ensure printers, USB devices, or other peripherals are connected to both systems for testing
hardware compatibility.
D. Re-testing and Regression Testing:
1. Initial Testing: Perform all planned test cases on both OS versions,
recording any discrepancies in performance, UI issues, or feature
malfunctions.
2. Bug Fixes: If compatibility issues are identified (e.g., UI elements
misaligning on Windows 11), developers fix the issues.
3. Re-testing: After bug fixes, re-test the affected test cases on both OS
versions to verify that the issues are resolved.
4. Regression Testing: Run the entire test suite again to ensure that no
new issues have been introduced by the fixes.
• Ensure that all features continue to function properly on both OS
versions.
Challenges In Compatibility Testing

• Environment Diversity: Managing a wide range of configurations

and devices can be overwhelming.
• Resource Intensive: Acquiring and maintaining physical devices
or emulators is resource-heavy.
• Dynamic Updates: Keeping up with frequent updates in browsers,
OSs, and devices.
• Cost Considerations: Testing across multiple environments
increases cost and effort.
Strategies to Overcome Challenges
• Use cloud-based testing tools (e.g., BrowserStack,
Sauce Labs) for access to diverse environments without
needing physical devices.
• Stay informed about upcoming releases of target
environments
• Use cost-effective cloud-based solutions instead of
physical devices and setups.
Security testing
Identify Vulnerabilities
Assess the Effectiveness of Security Controls
Network security testing tools help identify vulnerabilities in
networks and systems. Some examples of these tools include:

• Metasploit
A framework that automates tasks to identify
vulnerabilities in a targeted system

• Wireshark
A network protocol analyzer that examines network traffic
in real-time to identify vulnerabilities

• Nessus
A cross-platform vulnerability scanner that provides
information on exploitation and remediation for identified
vulnerabilities
• OpenVAS is an open-source vulnerability scanner that tests
network-connected devices for vulnerabilities.

• Aircrack-ng
A tool that identifies and exploits vulnerabilities in Wi-Fi
networks, particularly WEP and WPA/WPA2-PSK security
protocols

• John the Ripper

A password cracking tool that finds weak passwords on a
given system

• Kali Linux
A penetration testing tool that scans IT systems and network
vulnerabilities