Software Validation and Testing

TEST PLAN
Software Validation and Testing

Table of Content

1. Overview………………………………………………….………3
1.1 Objectives
1.2 Scope
1.3 Testing Environment

2. Test Deliverables…….………………………………………….5
2.1 Test Documentation Includes
2.2 Testing Schedule

2.3 Features That Are Expected to Be Tested

2.4 Possible Risks and Mitigation

3. Rules and Responsibilities ……………………………….…8

4. Test Completion Criteria………….………………………...9

4.1 Suspension Criteria
4.2 Exit Criteria

2
Software Validation and Testing

1. Overview:
Our e-commerce platform is a modern hub for laptops and phones, targeting a broad audience but
emphasizing individuals aged 12 to 35 with a focus on trendy devices. The website features a sleek design and a
user-friendly interface, including a secure login/register page for enhanced engagement. Prominent
sponsorships from brands like Coca-Cola, Philips, and PayPal add credibility to the platform. The product range
is diverse, showcasing innovative laptops and phones. Customer trust is established through reviews, while
social media integration aids in marketing. Discounts and promotions incentivize purchases, and security
measures protect user data. And the colorful visuals of the website resonate with the younger demographic.
Innovative payments add value, and loyalty programs reward customers. User surveys provide insights, and
dynamic product pages make your platform competitive in online tech retail.

1.1 Objectives:
The key testing objectives aligned with the features and functionalities of the website:
1- Functional Testing:
-Objective: Validate that all features and functionalities work according to specified requirements.
- Ensure seamless navigation, accurate product displays, and functional search and filtering options.
2- Usability Testing:
- Objective: Evaluate the user interface for intuitiveness and overall user experience.
- Confirm that the design is user-friendly, promoting easy navigation and positive interaction.
3- Security Testing:
Objective: Identify and address potential vulnerabilities and ensure the protection of user data.
4- Error Handling Testing:
Objective: Validate how the website handles errors and unexpected scenarios.
5- Documentation Verification:
- Objective: Confirm that documentation accurately reflects the current state of the application.
- Ensure that users and developers have accurate and up-to-date information.

3
Software Validation and Testing
1.2 Scope:
Security: Assess the security measures to identify and address potential vulnerabilities.
Usability: Verify that the application is user-friendly and meets the usability standards.
Performance and scalability: Test the system's performance and scalability to ensure it can handle
growth in terms of users or data.
Error Handling: Validate how the system handles errors and edge cases.
Out of scope?
Testing Approach:
Manual Testing:
Functional Testing: Verify core features manually.
Usability Testing: Assess user experience manually.
Automated Testing:
Functional Testing: Automate repetitive and critical cases.
Performance Testing:
Load Testing: Simulate user loads to assess response.
Stress Testing: Evaluate stability under extreme conditions.
Scalability Testing: Ensure the system handles growth.
Security Testing:
Vulnerability Scanning: Security testing was conducted on our e-store website to assess vulnerabilities
and ensure the protection of user data and sensitive information.

1.3 Testing Environment:

Browser: Google Chrome
Operating System: Compatible with Chrome (Windows, MacOS, Linux)
Devices: Desktops and laptops with Chrome installed
Tools: Python and Selenium for automated testing
Performance Tools: Apache JMeter

4
Software Validation and Testing
2. Test Deliverables:
Test cases will be written for the Product button, Account button, Home button, Checkout button, boxes in the
checkout form, add to cart button (Including all 9 add to cart buttons), delete button after adding to the cart,
and login and register buttons.

2.1 Test Documentation includes:

1- Test cases.
2- Test report
3- Test codes

2.2 Testing Schedule:

Phase 1: Test Planning
Define test objectives and scope.
Identify testing resources and requirements.
Develop test cases and test data.

Phase 2: Unit Testing

Testers perform unit testing on individual components.
Identify and fix any code-level issues.
Ensure proper integration of modules.

Phase 3: Integration Testing

Test the integration of different modules.
Verify data flow and interactions between components.
Address any integration issues.

5
Software Validation and Testing
Phase 4: System Testing
Test the complete system in a controlled environment.
Validate system functionality against requirements.
Identify and resolve any system-level issues.

Phase 5: Functionality Testing

Comprehensive testing of all website functionalities.
Identify and address any functional issues.

Phase 6: Performance Testing

Assess website performance under different loads.
Identify and optimize areas of concern.
Ensure the website can handle expected user traffic.

Phase 7: User Acceptance Testing (UAT)

Engage end-users to test the website.
Gather feedback on usability and overall user satisfaction.
Make necessary adjustments based on user feedback.

Phase 8: Security Testing

Conduct a brief security assessment.
Implement necessary security measures.
Ensure compliance with basic security standards.

6
Software Validation and Testing

Phase 9: Regression Testing

Re-run selected test cases to ensure new changes didn't introduce issues.
Verify that previously identified issues have been resolved.

Phase 10: Final Review and Documentation

Conduct a final review of the entire testing process.
Document the test cases used, test results, and resolutions.
Prepare a final testing report and defect report.

2.3 Features that are expected to be tested:

1. Functional testing
2. Performance testing
3. Security testing
4. Usability testing

2.4 Possible Risks and Mitigation:

Risks Mitigation

Lack of time Do as many cases as we can

Limited information Meeting regularly with the developers.

Lack of experience Try to learn about testing as we can

Compatibility issues with tools regularly updating testing tools and

verifying compatibility with the website's
technology stack

7
 Software Validation and Testing
2.5 Test execution:
To accomplish all test types specified, there are requirements that a test engineer will require. These
are:
Identify the test environment.
Set up the test environment.
Execute the test cases.
Analyse the test result.
Report the test result.

3. Roles and Responsibilities:

The project manager assigned the development team and gave them the requirements for creating the website
and then testing it.
Also, documenters were assigned to follow up with the testers and document as they are getting forward in
their tasks.
The test manager gave the required tasks to the test engineers which were to write the test cases make sure to
write every step in specific detail and write the required test codes in Selenium with the help of the test
manager by providing the resources and guiding through the process of the manual testing and the automating.

ROLES
Project Manager Mohammad Jada

Test Manager Raya Halwani

Test Engineers Mohammad Hamdani/Osama Alnajjar

Test Leader Mohammad Jada

Testers Raya Halwani/ Mohammad Hamdani/ Osama Alnajjar/ Mohammad Jada

UI manager Osama Alnajjar

UI designer Mohammad Jada/Raya Halwani/Mohammed Amine/ Mohammad Hamdani

Developers SOHAIB JAYOUSI/Mohammed Aburahma

Documenters Mohammad Jada/Mohammed Harrari/Ahmad Musleh/Khaled Hussein Ali

presenter Ghaith Arafaai

8
Software Validation and Testing

Defect Management:
For our website's defect management, the process begins with team members reporting issues, utilizing a
standardized format.

Collaborative review meetings involve the entire team in discussing, prioritizing, and assigning defects.
Developers investigate reported defects, working closely with testers to identify root causes. Detailed
resolution proposals are provided, outlining steps and timelines.

Testers give a lot of time and work to verify resolutions, seeking approval from both the overseeing team leader
and testing teams before closure.

Detailed documentation is maintained throughout the process for reference.

Defects are prioritized for deployment based on severity, what that means is that the harder and the bigger the
problem is, the more time and more priority is given to solving it by the team members.

4. Test Completion Criteria

4.1 Suspension Criteria
50% of test cases FAILED.
If the team members report that 50% of test cases failed, suspend testing until the development team
fixes all the failed cases.

4.2 Exit Criteria

outlines the criteria for what marks a test phase's successful completion.
- Run rate is mandatory to be 100% unless a clear reason is given.
- Pass rate is 80%, achieving the pass rate is mandatory

4.3 Review and Approval:

All documents will be approved by the test engineers, test manager, and project manager.

9
References:
Try and catch / finally https://www.browserstack.com/guide/exceptions-in-selenium-webdriver

Selenium basic tutorials and instructions

https://youtube.com/playlist?list=PLzMcBGfZo4-n40rB1XaJ0ak1bemvlqumQ&si=7VhVUmrDtPO8zhDt

Udemy, learn selenium automation in easy python.

https://www.udemy.com/course/learn-selenium-automation-in-easy-python-language/

All labs related to selenium are included in the course.

10