0% found this document useful (0 votes)
8 views5 pages

Ccs366 Software Testing and Automation Laborator

Uploaded by

14gunarajan
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)
8 views5 pages

Ccs366 Software Testing and Automation Laborator

Uploaded by

14gunarajan
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

CCS366 SOFTWARE TESTING AND AUTOMATION LABORATOR

Experiment 1: Develop the Test Plan for Testing an E-commerce Web/Mobile Application (www.amazon.in)

Aim:
The aim of this experiment is to develop a comprehensive test plan for testing the functionality and
usability of the e-commerce web/mobile application www.amazon.in.

Algorithm:
1. Identify the Scope: Determine the scope of testing, including the features and functionalities
that need to be tested.
2. Define Test Objectives: Specify the primary objectives of testing, such as functional testing,
usability testing, performance testing, security testing, etc.
3. Identify Test Environment: Define the platforms, browsers, devices, and operating systems
on which the application will be tested.
4. Determine Test Deliverables: Decide on the documents and artifacts that will be generated
during the testing process, such as test cases, test reports, and defect logs.
5. Create Test Strategy: Develop an overall approach for testing, including the testing
techniques, entry and exit criteria, and the roles and responsibilities of the testing team.
6. Define Test Scope and Schedule: Specify the timeline for each testing phase and the scope of
testing for each phase.
7. Risk Analysis: Identify potential risks and their impact on the testing process, and devise risk
mitigation strategies.
8. Resource Planning: Allocate the necessary resources, including the testing team, hardware,
and software required for testing.
9. Test Case Design: Prepare detailed test cases based on the requirements and functionalities
of the e-commerce application.
10. Test Data Setup: Arrange test data required for executing the test cases effectively.
11. Test Execution: Execute the test cases and record the test results.
12. Defect Reporting: Document any defects encountered during testing and track their
resolution.
Test Plan:
The test plan should cover the following sections:
1. Introduction: Briefly describe the purpose of the test plan and provide an overview of the e-
commerce application to be tested.
2. Test Objectives: List the primary objectives of testing the application.
3. Test Scope: Specify the features and functionalities to be tested and any limitations on
testing.
4. Test Environment: Describe the hardware, software, browsers, and devices to be used for
testing.
5. Test Strategy: Explain the overall approach to be followed during testing.
6. Test Schedule: Provide a detailed timeline for each testing phase.
7. Risk Analysis: Identify potential risks and the strategies to mitigate them.
8. Resource Planning: Specify the resources required for testing.
9. Test Case Design: Include a summary of the test cases developed for the application.
10. Test Data Setup: Describe the process of arranging test data for testing.
11. Defect Reporting: Explain the procedure for reporting and tracking defects.

Test Case Table:

Actual
Result
Expecte d Commen
Proces s No. Test Case Steps Description Status Result t

Test Plan
1. Review Verify the The test plan
Scope of the test plan scope of includes all
TC001 Testing document. testing. Done features.

1. Review Verify the test The test


Test the test plan objectives active s are
TC002 Objective s document. . Done well-defined.
Check the
Test 1. Review specified Test
Environmen the test plan environments environment
TC003 t document. . Done s are mentioned.

Ensure all The test


1. Review
deliverable s active s are
Test the test plan well defined.
document. are listed.
TC004 Deliverable s Done .

The test
Verify the
1. Review strategy is
overall
Test the test plan clearly
approach.
TC005 Strateg y document. Done stated.

Test 1. Review Check the The schedule


Scope and the test plan schedule and and scope are
TC006 Schedule document. scope. Done defined.

Risks and
1. Review Ensure potential mitigation
Risk the test plan risks are strategies are
TC007 Analysi s document. identified. Done mentioned.

Check Resources
1. Review needed
the test plan the required
Resource resources for testing are
document. listed.
TC008 Planning . Done

1. Review and Validate the Test cases are


Test execute the prepared test accurate and
Case test cases. cases. functional.
TC009 Design Done

1. Review the Verify the Test data is


Test test data setup availability of available for
Data process. test data. testing.
TC010 Setup Done
1. Run the
test cases Test results are
and recorded and
Test document Execute the In documented
TC011 Executio n the outcomes. test cases. Progres s .

1. Log defects Ensure Defects are


with detailed defects are reported with
Defect information reported Not sufficient
TC012 Reportin g . correctly. Started details.

Defects are
1. Monitor Verify the
Not tracked until
Defect defect status tracking of
Started resolution.
TC013 Trackin g and updates. defects.

Explanation:
The test plan is a crucial document that outlines the entire testing process. It ensures that all aspects
The ecommerce applications are throughly tested.and the result are systemeticaly documented

Result:

Thus the program was tested and got the output successfully and got verified

Experiment 2: Design the Test Cases for Testing the E-commerce Application

Aim:
The aim of this experiment is to design a set of comprehensive and effective test cases for testing the e-
commerce application www.amazon.in.

Algorithm:
1. Understand Requirements: Familiarize yourself with the functional and nonfunctional
requirements of the e-commerce application.
2. Identify Test Scenarios: Based on the requirements, identify different test scenarios that
cover all aspects of the application.
3. Write Test Cases: Develop test cases for each identified scenario, including preconditions,
steps to be executed, and expected outcomes.
4. Cover Edge Cases: Ensure that the test cases cover edge cases and boundary conditions to
verify the robustness of the application.
5. Prioritize Test Cases: Prioritize the test cases based on their criticality and relevance to the
application.
6. Review Test Cases: Conduct a peer review of the test cases to ensure their accuracy and
completeness.
7. Optimize Test Cases: Optimize the test cases for reusability and maintainability.

Test Case Design:


The test case design should include the following components for each test case:

1. Test Case ID: A unique identifier for each test case.


2. Test Scenario: Description of the scenario being tested.
3. Test Case Description: Detailed steps to execute the test.

4. Precondition: The necessary conditions that must be satisfied before executing the test case.

5. Test Steps: The sequence of actions to be performed during the test.

6. Expected Result: The outcome that is expected from the test.

You might also like