Software Testing Project
Software Testing Project to practice Manual Testing, automated testing using Selenium or UFT. Software Test Requirements, Software Test Scenarios, Software Test Cases, Software Test Execution, and Test Life Cycle Closure.
Software Testing Live Project
Software Testing Live Project
Software Testing Live Project URLs for Practicing, You can use Manual Testing, or Automated Testing for Testing this Project.
Software Testing point of view, we have three interfaces for any Software Application, Admin Interface, User Interface, and Database Interface.
Software Testing Project Admin Interface URL
(Server side Interface)
(The admin interface is project’s primary control panel, once logged in, user can use the admin interface to set up and configure a project, manage its structure and content, install extensions, and perform other tasks.)
Username: gcreddy
Password:[email protected]
Test Cases for Automation:
Test Case 1: Verify Admin Login Functionality in gcrShop application Admin interface
Test Steps:
i) Launch the Browser
ii) Navigate to gcrShop Admin Interface (“http://gcreddy.com/project/admin/login.php”)
iii) Enter “Username”
iv) Enter “Password”
v) Click “Login Button
Verification Point/s:
Capture the current URL after Login and compare with expected
//or
Verify the existence of “Log Off” Link
Input / Test Data:
Username: gcreddy
Password: [email protected]
Expected Result:
“http://gcreddy.com/project/admin/index.php”
Actual Result: * After Execution
Test Result: Pass / Fail (* After Execution)
Comments: Optional
Test Case 2: Verify “Redirect” Functionality from Admin to User Interface in gcrShop application
Test Steps:
i) Launch the Browser
ii) Navigate to gcrShop Admin Interface (“http://gcreddy.com/project/admin/login.php”)
iii) Click “Online Catalog” Link
Verification Point
Capture the current URL and compare with expected
Expected:
“http://gcreddy.com/project/”
Test Data:
NA
Test Case 3: Verify Admin Login, Or Error Message in Login Functionality in gcrshop application
Test Steps:
i) Launch the Browser
ii) Navigate to (Load) gcrshop admin interface login page /home page (“http://gcreddy.com/project/admin/login.php”)
iii) Enter “Username”
iv) Enter “Password”
v) Click “Login” Button
Verification Points
i) Capture the current URL after Login and compare with expected
ii) Capture the “Error Message” if login fails and compare with expected
Expected Result:
“http://gcreddy.com/project/admin/index.php”
Error: Invalid administrator login attempt.
Input / Test Data:
i) Test Data for Positive Scenario
a) Username: gcreddy
b) Password: [email protected]
ii) Test Data for Negative Scenario 1:
a) Username: abcdef
b) Password: [email protected]
iii) Test Data for Negative Scenario 2:
a) Username: gcreddy
b) Password: [email protected]
iv) Test Data for Negative Scenario 3:
a) Username: abcdef
b) Password: [email protected]
v) Test Data for Negative Scenario 4:
a) Username: gcreddy
b) Password:
vi) Test Data for Negative Scenario 5:
a) Username:
b) Password: [email protected]
vii) Test Data for Negative Scenario 5:
a) Username:
b) Password:
Test Case 4: Write a Test case for Admin Login Locking Functionality in gcr Shop application admin interface.
(Business Rule: Admin Login will be locked for 5 minutes after 3 failed login attempts)
Test Steps:
i) Launch the Browser
ii) Navigate to (Load) gcrshop admin interface login page /home page (“http://gcreddy.com/project/admin/login.php”)
iii) Enter “Username”
iv) Enter “Password”
v) Click “Login” Button
Verification Point
Capture the Error message and compare with expected for 4 times
Expected:
1st iteration: Error: Invalid administrator login attempt.
2nd iteration: Error: Invalid administrator login attempt.
3rd iteration: Error: Invalid administrator login attempt.
4th iteration: Error: The maximum number of login attempts has been reached. Please try again in 5 minutes.
Software Testing Project User Interface URL
(Client side Interface)
(Visual part of computer application, through which a user interacts with a computer or a software. It determines how commands are given to the computer or the program and how information is displayed on the screen.)
Note: In Client side Interface of this application, guest use can create (register with site) login and Login to the application.
Project Information
Project Domain: Ecommerce
Sub-Domain: B2C (Business to Customer)
Application: Online Shopping Portal
Application Development Environment: LAMP (Linux, Apache, MySQL and PHP)
Production Environment: Internet (Public Web Application)
Test Environment: Intranet
Test Type: Functional Testing
Note: Use this sample project for practicing Functional Testing.
Software Test Method: Manual Testing / Automated Testing (using Selenium)
Note: This Project for practice, so You can use Manual Testing or Automated Testing
Project Overview
i) Admin Interface/Server side (Application Master Data (Add/Edit/Delete), and Maintenance (User management, Operations management etc…) of the application
ii) User Interface/Clint side: Perform specified Business operations
Admin Interface:
Add / Edit/Delete Manufacturer/s
Add/Edit/delete Category/s
Add / Edit/Delete Product/s
Add / Edit/Delete/Set as Default Currency
Reports
User Interface
View Products, Product Search, Advanced Search
Customer Registration, Customer Login,
Shopping Cart (Add Product/s, Update Quantity, Remove Product….)
Checkout (Change Address, Add Comments, Payment Method, Edit Details, Order Confirmation…)
Stakeholders of the Project
An individual, group, or organization, who may effect, be affected by, or perceive itself to be affected by a decision or activity, or outcome of a project
Project Leader
Senior Management
Project Team Members
Project Customer
Project Testers
Subcontractors, Consultants etc…
Interfaces of the Project/AUT
Three Interfaces of Software Application,
i) Admin Interface
ii) User Interface
iii) Database Interface
i) Admin Interface:
“http://gcreddy.com/project/admin/login.php”
Username: gcreddy
Password: [email protected]
2) User Interface
“http://gcreddy.com/project/”
