V.S.B.

ENGINEERING COLLEGE KARUR

(An Autonomous Institution)
DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING
INTERNAL TEST-II ANSWER KEY
CCS366-SOFTWARE TESTING AND AUTOMATION
PART-A
1) What is path testing, and how does it differ from other testing techniques?
● Path testing is a structural testing method that involves using the source code of a program
to attempt to find every possible executable path.
● The idea is that we are then able to test each individual path in as many ways as possible
in order to maximise the coverage of each test case.
.
2) How can effective organization and tracking of test cases enhance project management and
ensure comprehensive test coverage?
● Test case management helps to organise and execute the cases that validate individual
software functions or features.
● It ensures comprehensive coverage by mapping test cases to specific features and tracking
their execution and results.

3) Define the concept of equivalence class testing and its benefits in test design.
● Equivalence class testing, also known as equivalence partitioning (ECP), is a software
testing technique that groups input data into partitions to reduce the number of test cases
needed to validate a system's behavior.
● Benefits of equivalence class testing:
● Reduces testing effort
● Useful when exhaustive testing isn't practical
4) How does volume testing differ from load testing?
● Volume testing is a software testing performed to test the system under huge data load.
● Load testing is a software testing performed to test the performance of the system under
real life load.
● Data loss is tested during volume testing.
5) Give the examples of security testing. Examples of Security Testing:

1. Vulnerability Scanning: Automated tools scan for known vulnerabilities.

2. Penetration Testing: Simulating attacks to find security weaknesses.
3. SAST: Analyzing source code for vulnerabilities.
4. DAST: Testing running applications for real-time vulnerabilities.
5. Security Auditing: Reviewing security policies and controls.

PART-B
6 (a) (i) Explain about test objective identification of test design and execution.

Identifying Test Objectives in Test Design and Execution:

Test Design:

1. Understanding Requirements:
○ Gather Requirements: Collaborate with stakeholders to understand the business
needs, user expectations, and technical specifications.
○ Define Scope: Clearly outline the features and functionalities that will be included
in the testing process.
2. Setting Clear Goals:
○ Functional Objectives: Ensure that the software performs its intended functions
correctly.
○ Non-Functional Objectives: Include performance, security, usability, and
compatibility testing.
 3. Risk Assessment:
○ Identify Risks: Determine potential risks and areas prone to defects.
○ Prioritize Testing: Focus on high-risk areas to ensure critical functionalities are
thoroughly tested.
4. Defining Success Criteria:
○ Acceptance Criteria: Establish what constitutes a successful test, such as specific
performance benchmarks or zero critical defects.
○ Exit Criteria: Determine the conditions under which testing can be considered
complete.
5. Documenting Objectives:
○ Test Plan: Create a comprehensive test plan that includes all identified objectives,
scope, resources, and timelines.

Test Execution:

1. Preparation:
○ Test Environment Setup: Ensure that the test environment is configured correctly
and mirrors the production environment as closely as possible.
○ Test Data Preparation: Create and manage test data that will be used during the
testing process.
2. Executing Tests:
○ Test Case Execution: Run the test cases as per the test plan.
○ Monitoring and Logging: Monitor the system’s behavior and log any defects or
issues encountered.
3. Defect Management:
○ Reporting Defects: Document any defects found during testing, including steps
to reproduce, severity, and impact.
○ Tracking and Resolution: Track the progress of defect resolution and retest once
fixes are applied.
4. Review and Analysis:
○ Test Results Analysis: Analyze the results of the test execution to determine if the
objectives have been met.
○ Metrics and Reporting: Collect metrics such as test coverage, defect density, and
test execution progress to report to stakeholders.
5. Continuous Improvement:
○ Feedback Loop: Use the insights gained from test execution to refine test
objectives and improve future test designs.
○ Adaptation: Adjust test objectives as needed based on changes in project scope,
requirements, or identified risks.

Evolution of Test Objectives:

1. Initial Phase:
○ Broad Objectives: Start with high-level objectives based on initial requirements
and project scope.
○ Baseline Testing: Focus on basic functionality and initial performance
benchmarks.
2. Development Phase:
○ Refinement: As the project progresses, refine objectives based on new insights,
changes in requirements, and feedback from early testing.
○ Incremental Testing: Continuously test new features and integrations as they are
developed.
3. Testing Phase:
○ Detailed Objectives: Develop more detailed and specific objectives as the
software nears completion.
 ○ Comprehensive Testing: Conduct thorough testing, including regression,
performance, and security testing.
4. Pre-Release Phase:
○ Final Adjustments: Adjust objectives based on final user feedback and any last-
minute changes.
○ Acceptance Testing: Ensure all acceptance criteria are met before the software is
released.

5. Post-Release Phase:
○ Ongoing Objectives: Continue to monitor and test the software for any issues that
arise in the production environment.
○ Maintenance Testing: Update objectives to include testing for patches, updates,
and new features.

Importance of Adapting Test Objectives:

1. Respond to Changes: Software projects often undergo changes in requirements, scope,

and timelines. Adapting test objectives ensures that testing remains relevant and
effective.
2. Improve Quality: Continuously refining objectives helps identify and address new risks
and defects, leading to higher software quality.
3. Stakeholder Alignment: Keeping test objectives aligned with evolving business goals
and user expectations ensures that the final product meets stakeholder needs.
4. Efficient Resource Use: Adapting objectives helps prioritize testing efforts, ensuring
that resources are focused on the most critical areas.

6 (a) (ii) In the context of a large-scale software testing project, discuss the interplay between
test design factors like time, budget, and available resources. How can test managers
make informed decisions to balance these factors and ensure successful testing?
Interplay Between Test Design Factors:

In large-scale software testing projects, balancing time, budget, and available resources is crucial.
These factors are interdependent, and changes in one can significantly impact the others. Here’s
how they interplay and how test managers can make informed decisions:

Time:

● Project Deadlines: Tight deadlines can limit the extent of testing, potentially
compromising quality.
● Testing Phases: Allocating sufficient time for different testing phases (unit, integration,
system, acceptance) is essential.
● Iteration Cycles: Agile methodologies require frequent testing cycles, impacting overall
time management.

Budget:

● Resource Allocation: Budget constraints can limit the number of testers, tools, and
environments available.
● Tool Licenses: Investing in automated testing tools and infrastructure can be costly but
may save time in the long run.
● Outsourcing: Sometimes, outsourcing parts of the testing process can be a cost-effective
solution.
Available Resources:

● Human Resources: The skill level and availability of testers can affect the quality and
speed of testing.
● Testing Tools: The availability of appropriate testing tools and environments is critical
for effective testing.
● Infrastructure: Adequate hardware and network resources are necessary to simulate
real-world conditions.

Balancing These Factors:

Prioritization:

● Risk-Based Testing: Focus on testing the most critical and high-risk areas of the
application first.
● Requirement Analysis: Prioritize test cases based on the importance and impact of the
features being tested.

Efficient Resource Management:

● Skill Utilization: Assign tasks based on the testers’ expertise to maximize efficiency.
● Automation: Use automated testing to handle repetitive tasks, freeing up human
resources for more complex testing.
● Cross-Training: Train team members in multiple areas to ensure flexibility and better
resource utilization.

Time Management:

● Test Planning: Develop a detailed test plan with clear timelines and milestones.
● Parallel Testing: Conduct parallel testing activities to save time, such as running
automated tests while manual testing is ongoing.
● Continuous Integration: Implement continuous integration and continuous testing
practices to identify issues early and reduce rework.

Budget Optimization:

● Cost-Benefit Analysis: Evaluate the cost versus the benefit of different testing activities
and tools.
● Open-Source Tools: Utilize open-source testing tools where possible to reduce costs.
● Outsourcing: Consider outsourcing non-critical testing tasks to manage budget
constraints effectively.

Adapting Objectives:
Continuous Monitoring:

● Progress Tracking: Regularly track progress against the test plan and adjust as needed.
● Feedback Loops: Incorporate feedback from testing phases to refine objectives and
strategies.

Flexibility:

● Scope Adjustment: Be prepared to adjust the scope of testing based on time and budget
constraints.
● Iterative Improvement: Continuously improve testing processes based on lessons
learned and evolving project needs.
6. (b) Explain the process of identifying test objectives in the context of a complex software
project. How do these objectives evolve throughout the project life cycle, and why is it
important to adapt them as needed?
Identifying Test Objectives in a Complex Software Project:
Process of Identifying Test Objectives:

1. Understand Project Requirements:

○ Gather Requirements: Collaborate with stakeholders to understand the business
requirements, user expectations, and technical specifications.
○ Define Scope: Clearly outline what features and functionalities will be included
in the testing process.
2. Set Clear Goals:
○ Functional Objectives: Ensure that the software performs its intended functions
correctly.
○ Non-Functional Objectives: Include performance, security, usability, and
compatibility testing.
3. Risk Assessment:
○ Identify Risks: Determine potential risks and areas prone to defects.
○ Prioritize Testing: Focus on high-risk areas to ensure critical functionalities are
thoroughly tested.
4. Define Success Criteria:
○ Acceptance Criteria: Establish what constitutes a successful test, such as
specific performance benchmarks or zero critical defects.
○ Exit Criteria: Determine the conditions under which testing can be considered
complete.
5. Document Objectives:
○ Test Plan: Create a comprehensive test plan that includes all identified
objectives, scope, resources, and timelines.

Evolution of Test Objectives Throughout the Project Life Cycle:

1. Initial Phase:
○ Broad Objectives: Start with high-level objectives based on initial requirements
and project scope.
○ Baseline Testing: Focus on basic functionality and initial performance
benchmarks.
2. Development Phase:
○ Refinement: As the project progresses, refine objectives based on new insights,
changes in requirements, and feedback from early testing.
○ Incremental Testing: Continuously test new features and integrations as they are
developed.
3. Testing Phase:
○ Detailed Objectives: Develop more detailed and specific objectives as the
software nears completion.
○ Comprehensive Testing: Conduct thorough testing, including regression,
performance, and security testing.
4. Pre-Release Phase:
○ Final Adjustments: Adjust objectives based on final user feedback and any last-
minute changes.
○ Acceptance Testing: Ensure all acceptance criteria are met before the software
is released.
5. Post-Release Phase:
○ Ongoing Objectives: Continue to monitor and test the software for any issues
that arise in the production environment.
 ○ Maintenance Testing: Update objectives to include testing for patches, updates,
and new features.

Importance of Adapting Test Objectives:

1. Respond to Changes: Software projects often undergo changes in requirements, scope,

and timelines. Adapting test objectives ensures that testing remains relevant and
effective.
2. Improve Quality: Continuously refining objectives helps identify and address new risks
and defects, leading to higher software quality.
3. Stakeholder Alignment: Keeping test objectives aligned with evolving business goals
and user expectations ensures that the final product meets stakeholder needs.
4. Efficient Resource Use: Adapting objectives helps prioritize testing efforts, ensuring that
resources are focused on the most critical areas.
By identifying and evolving test objectives throughout the project life cycle, teams can ensure
comprehensive and effective testing, leading to a high-quality software product.

7. (a) (i) Illustrate the concept of usability testing with an example.

Usability Testing:
Usability testing is a technique used to evaluate a product by testing it with real users. The goal
is to observe how easily users can navigate the product, understand its features, and achieve their
goals. This helps identify any usability issues and areas for improvement.
Example of Usability Testing:
Imagine a company developing a new online grocery shopping website. They want to ensure
that users can easily find and purchase groceries. Here’s how they might conduct usability
testing:

1. Test Planning:
○ Objective: To evaluate the ease of use of the website’s shopping and checkout
process.
○ Participants: Recruit a diverse group of users who represent the target audience,
such as busy parents, working professionals, and elderly individuals.
2. Test Scenarios:
○ Scenario 1: A user wants to find and purchase a specific brand of cereal.
○ Scenario 2: A user needs to add multiple items to their cart and apply a discount
code at checkout.
○ Scenario 3: A user wants to schedule a delivery for a specific date and time.
3. Execution:
○ Task Assignment: Each participant is given a set of tasks to complete based on
the scenarios.
○ Observation: Test facilitators observe the participants as they navigate the
website, noting any difficulties or confusion.
○ Think-Aloud Protocol: Participants are encouraged to verbalize their thoughts
and actions while using the website, providing insights into their decision-making
process.
4. Data Collection:
○ Qualitative Data: Collect feedback on user satisfaction, ease of navigation, and
any issues encountered.
○ Quantitative Data: Measure task completion times, error rates, and the number
of clicks required to complete tasks.
5. Analysis:
○ Identify Issues: Analyze the data to identify common usability problems, such as
confusing navigation, unclear instructions, or slow loading times.
○ Prioritize Fixes: Determine which issues have the most significant impact on
user experience and prioritize them for resolution.
 6. Reporting:
○ Usability Report: Compile a report detailing the findings, including specific
usability issues, user feedback, and recommendations for improvement.
7. Iteration:
○ Implement Changes: Make the necessary changes to the website based on the
usability testing results.
○ Re-Test: Conduct additional usability tests to ensure that the changes have
resolved the issues and improved the user experience.

By conducting usability testing, the company can ensure that their online grocery shopping
website is user-friendly, efficient, and meets the needs of their customers.

7. (a) (ii) Discuss about volume testing with an example.

Volume testing is a type of performance testing that evaluates how a system handles a large
volume of data. The primary goal is to ensure that the application can manage high data loads
without performance degradation, data loss, or system crashes.
Key Objectives of Volume Testing:
1. Verify Data Integrity: Ensure that the system does not lose or corrupt data when handling
large volumes.
2. Check System Performance: Assess the response time and overall performance under
heavy data loads.
3. Identify Bottlenecks: Detect any performance bottlenecks or issues that arise due to high
data volume.
4. Ensure Stability: Confirm that the system remains stable and does not crash
unexpectedly.
Example of Volume Testing:
Consider an e-commerce website preparing for a major sale event. The testing team wants to
ensure that the website can handle a significant increase in data volume, such as a large number
of product listings and user transactions.

1. Scenario Setup:
○ Data Preparation: Populate the database with a large number of product listings,
user accounts, and transaction records.
○ Simulate User Activity: Use automated tools to simulate thousands of users
browsing products, adding items to their carts, and completing purchases
simultaneously.
2. Execution:
○ Monitor Performance: Track the website’s response times, server load, and
database performance during the test.
○ Check Data Integrity: Verify that all transactions are processed correctly and no
data is lost or corrupted.
3. Analysis:
○ Identify Issues: Look for any performance bottlenecks, slow response times, or
system crashes.
○ Optimize: Make necessary adjustments to the database, server configurations, or
application code to improve performance.
4. Re-Test:
○ Repeat Testing: Conduct additional volume tests to ensure that the optimizations
have resolved the identified issues and the system can handle the expected data
volume.

By performing volume testing, the e-commerce website can ensure that it remains functional and
responsive even during peak usage times, providing a smooth user experience and maintaining
data integrity.
7. (b)How does the diversity of devices and browsers impact the testing process for web
applications and how is it distinct from mobile app testing?

Impact on Web Application Testing:

1. Browser Compatibility: Different browsers have unique rendering engines and support
various web standards to different extents. This can lead to discrepancies in how web
content is displayed and functions. Cross-browser testing ensures that a web application
provides a consistent user experience across all browsers.
2. Device Diversity: Users access web applications from a wide range of devices, including
desktops, laptops, tablets, and smart TVs. Each device has different screen sizes,
resolutions, and hardware capabilities. Testing on multiple devices ensures that the web
application looks good and functions properly on all of them.
3. Operating System Variations: Web applications need to be tested on different operating
systems (Windows, macOS, Linux) to identify and fix platform-specific issues.
4. Performance Metrics: Evaluating loading times and responsiveness across different
browsers and devices helps identify performance bottlenecks.
5. Accessibility Compliance: Ensuring the application is usable for individuals utilizing
assistive technologies, such as screen readers, is crucial.

Distinction from Mobile App Testing:

1. Platform-Specific Testing: Mobile app testing often involves testing on specific

platforms like iOS and Android, each with its own set of guidelines and requirements.
Web applications, on the other hand, need to be tested across a broader range of browsers
and devices.
2. App Store Guidelines: Mobile apps must comply with app store guidelines (Apple App
Store, Google Play Store), which include specific requirements for performance, security,
and user experience. Web applications do not have such centralized guidelines but must
ensure compatibility across various browsers and devices.
3. Network Conditions: Mobile apps are often used in varying network conditions (3G,
4G, Wi-Fi), requiring testing under different network scenarios. While web applications
also need to consider network performance, the focus is more on browser and device
compatibility.
4. User Interface and Experience: Mobile apps typically have a more streamlined user
interface optimized for touch interactions, whereas web applications need to cater to both
touch and non-touch interfaces.

PART-C
8 (a) Imagine you are testing a critical financial application. Describe a scenario where you
identify specific inputs and conditions where boundary value testing is essential to ensure
the software's reliability. Provide examples and discuss the implications of not performing
boundary value testing in this scenario.

Scenario: Online Fund Transfer

Specific Inputs and Conditions for Boundary Value Testing:

1. Transfer Amount Limits:

○ Minimum Transfer Amount: Testing with the smallest possible transfer amount
(e.g., ₹1).
○ Maximum Transfer Amount: Testing with the largest possible transfer amount
(e.g., ₹1,00,000).
○ Just Below Minimum: Testing with an amount just below the minimum (e.g.,
₹0).
 ○ Just Above Maximum: Testing with an amount just above the maximum (e.g.,
₹1,00,001).
2. Account Balance:
○ Minimum Balance Requirement: Testing with an account balance that meets
the minimum requirement (e.g., ₹500).
○ Just Below Minimum Balance: Testing with an account balance just below the
minimum requirement (e.g., ₹499).
○ Maximum Account Balance: Testing with the maximum account balance
allowed (e.g., ₹10,00,000).
3. Transaction Limits:
○ Daily Transfer Limit: Testing with the daily transfer limit (e.g., ₹2,00,000).
○ Just Below Daily Limit: Testing with an amount just below the daily limit (e.g.,
₹1,99,999).
○ Just Above Daily Limit: Testing with an amount just above the daily limit (e.g.,
₹2,00,001).

Examples:

1. Minimum Transfer Amount:

○ Input: ₹1
○ Expected Result: Successful transfer.
2. Just Below Minimum Transfer Amount:
○ Input: ₹0
○ Expected Result: Error message indicating the amount is too low.
3. Maximum Transfer Amount:
○ Input: ₹1,00,000
○ Expected Result: Successful transfer.
4. Just Above Maximum Transfer Amount:
○ Input: ₹1,00,001
○ Expected Result: Error message indicating the amount exceeds the limit.
5. Just Below Minimum Balance:
○ Input: Transfer ₹500 from an account with ₹499 balance.
○ Expected Result: Error message indicating insufficient funds.

Implications of Not Performing Boundary Value Testing:

● Undetected Errors: Without boundary value testing, edge cases might go unnoticed,
leading to potential failures in real-world scenarios.
● Financial Loss: Errors in handling minimum and maximum values could result in
incorrect transactions, causing financial loss to users or the bank.
● User Frustration: Users encountering errors during critical transactions may lose trust
in the application, leading to dissatisfaction and potential loss of customers.
● Regulatory Issues: Financial applications must comply with strict regulations. Failing
to handle boundary conditions properly could result in non-compliance and legal
consequences.

8.(b) Analyze fail over testing, recovery testing, configuration testing and compatibility
Testing..

1. Failover Testing
Failover Testing ensures that a system can seamlessly switch to a backup system in the event of
a failure. This type of testing is crucial for systems that require high availability and reliability.
It involves:
 ● Simulating Failures: Intentionally causing failures to test the system’s ability to switch
to a backup.
● Validating Recovery: Ensuring that the system can recover without data loss or
significant downtime.

2. Recovery Testing
Recovery Testing focuses on verifying the system’s ability to recover from crashes, hardware
failures, or other unexpected issues. This testing ensures that the system can restore operations
and recover data effectively. Key aspects include:

● Simulating Crashes: Intentionally causing system crashes to test recovery procedures.

● Backup and Restore: Testing the backup and restore processes to ensure data integrity..

3. Configuration Testing
Configuration Testing involves verifying the system’s performance and behavior under various
configurations. This includes testing different hardware, software, network settings, and other
environmental variables. The main goals are:

● Compatibility: Ensuring the system works correctly with different configurations.

● Performance: Assessing how different configurations impact system performance.
● Stability: Identifying any configuration-related issues that could affect system stability.

4. Compatibility Testing
Compatibility Testing checks whether the software application works as expected across
different environments, including various browsers, operating systems, devices, and network
environments. This testing ensures:

● Cross-Platform Functionality: Verifying that the application functions correctly on

different platforms.
● Backward Compatibility: Ensuring the application works with older versions of software
or hardware.
● Forward Compatibility: Testing the application with newer versions of software or
hardware to ensure future compatibility.