Skip to content

palatul16/Opencart

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

37 Commits
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

OPENCART - An e-commerce Gadget Store

It is an E-commerce Website based on electronics Gadget

image

INTRODUCTION

OpenCart is an e-commerce website for shopping electronics and digital items. Here, I perform functional, usability and performance testing, which ensures accuracy, efficiency, and quality.

PROJECT TYPE

Manual Testing

DEPLOYED WEBSITE

https://demo.opencart.com/

DIRECTORY STRUCTURE

=> Daily Practice of Manual Testing
=> Assignments
=> Daily DLC
=> Construct Week
=> Project
=> Test Plan
=> Mind Map
=> Test Scenario
=> Test Cases
=> Bug Report
=> Summary

CREDENTIALS

=> Username :- "qrst@gmail.com"
=> Password :- "1236"

SCOPE

Different Testing
Diiferent OS
Various Features

TESTED AREAS

Project.xlsx

TEST PLAN

Test Plan.docx

Bug Report.xlsx

TEST SUMMARY REPORT.docx

RECOMMENDATION AND SUGGESTION

Recommendations:

  1. Clarify Test Scope: Define exclusions like non-functional testing (e.g., security, performance).
  2. Specify Versions: List exact browser and OS versions to ensure cross-compatibility testing.
  3. Detail Testing Types: Break testing into functional, usability, and performance categories.
  4. Defect Tracking: Add severity levels (critical, major, minor) for defects to prioritize fixes.
  5. Consider Automation: Mention potential plans for automation in the future to scale the testing process.
  6. Performance Testing: If relevant, plan for performance tests like load and stress testing.

Suggestions:

  1. Test Case Design: Include edge cases, such as "insufficient funds" during gadget purchases.
  2. Communication Channels: Specify all communication methods (e.g., Slack, email, stand-ups) for better coordination.
  3. Entry/Exit Criteria: Refine phase entry/exit conditions to be more specific.
  4. Test Environment Setup: Mention specific server/database configurations and third-party integrations required.
  5. Risk Management: Identify potential challenges and solutions strategies.
  6. Version Control: Add versioning to track updates and changes to the test plan document.

FEEDBACK

If you have any feedback, Please contact to me atulpaldlehi@gmail.com

About

Manual Testing of an E-commerce Gadget store

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published