Selenium Live Project Part - 2

Software Testing Live Project Functional Test Automation using Selenium, Project Information, Project Description, Stake holders of the Project, Interfaces of the Project /AUT, Features to be Tested in Admin Interface, Features to be Tested in User Interface, Test Requirements, Test Scenarios, and Test Cases, Derive Smoke Test Cases for Admin Interface, Derive Smoke Test cases for User Interface, Derive Comprehensive (All Possible) Test Cases for Admin Interface, and Derive Comprehensive (All Possible) Test Cases for User Interface.

[gcreddy]

Class Notes:
5) Features to be Tested in Admin Interface

i) Launch the Application
ii) Admin Login to Application
iii) Redirect operation from Admin to User Interface
iv) Add/Edit/Delete Manufacturers
v) Add / Edit / Delete Categories
vi) Add / Edit / Delete Products
vii) Add/Edit/Delete/Set as default Currency
viii) User & Product Reports and Track Status

6) Features to be Tested in User Interface

i) Launch the Application
ii) Search, View Products
iii) Customer Registration
iv) Customer Login
v) Buy Products (Login, Buy Product/s, Update Quantity, delete products, Change the Details, payment option, checkout.)
vi) Track Order status

7) Test Requirements, Test Scenarios, and Test Cases.

Business Requirements
Software Requirements
Test Requirements
Test Scenarios (Positive & Negative)
Test Cases (* Test Data is required for some Test cases only)

Test Requirement/s
Functional Requirement
Non Functional Requirement
Performance Requirement
Load Test Requirement
Stress Test Requirement
Spike Test Requirement
Endurance Test Requirement...
Usability Testing
Reliability Testing
Localization Testing / Internationalization Testing
Availability Testing
Configuration Testing
Recovery Testing
Etc...

Functional Test Requirement
Ex: Admin user Login to Admin Interface of the Application

Test Scenarios:
i) Admin Login with valid Username, and Password (Positive Test Scenario)
ii) Admin Login with invalid Username, and valid Password (Login failed attempt) (Negative scenario 1)
iii) Admin Login with valid Username, and invalid Password (Login failed attempt) (Negative scenario 2)
iv) Admin Login with invalid Username, and invalid Password (Login failed attempt) (Negative scenario 3)
v) Admin Login with Blank Username, and valid Password (Login failed attempt) (Negative scenario 4)
vi) Admin Login with Valid Username, and Blank Password (Login failed attempt) (Negative scenario 5)
Etc...

Test Case:

Test Case ID: TC_Ad_001
Test Case Name/Description: Admin user Login to Admin Interface of the Application (gcrShop)
Test Suite Id: TS_Ad_01
Priority:
Pre-Condition:
Steps to be Executed:
Post-Condition:
Expected Result:
Hardware and Software:
Actual Result:
Status:

Test Data:
Username: admin

No Test Data for some Test Cases (NA)
Ex: Redirect from Admin to User Interface before Admin Login

8) Derive Smoke Test cases for Admin Interface

i) Verify Launch the Application (Admin Interface) with valid URL
ii) Verify Required Elements availability of Login Page
iii) Verify Admin Login with valid input data to Admin Interface of the Application
iv) Verify Required Elements availability of Admin index page (after Login)
v) Verify Add Manufacturer
vi) Verify Add Category
vii) Verify Add Product
viii) verify Add Currency
ix) Set default Currency
Etc...

9) Derive Smoke Test cases for User Interface

i) Verify Launch the User Interface of the Application with valid URL
ii) Verify Required Elements availability of User interface Homepage
iii) Verify Customer Registration to the Application with valid Input data
iv) Verify Customer Login to User Interface
v) Verify Add Product/s (Update Quantity...)
vi) Verify Change Customer Address details
vii) Verify Checkout
viii) Verify customer Track Order
Etc...

10) Derive Comprehensive (All possible test cases) Test cases for Admin Interface

i) Verify Launch the Application (Admin Interface) with valid URL
ii) Verify Required Elements availability of Login Page
iii) Verify Redirect from Admin to User Interface before Admin Login
iv) Verify Admin Login with valid input data to Admin Interface of the Application
v) Verify Redirect from Admin to User Interface After Admin Login
vi) Verify Admin Login with Invalid input data (Login failed attempt) to Admin Interface of the Application
vii) Verify Admin Failed Login Attempt after 3 Failed attempts
viii) Verify Admin Login with valid input data to Admin Interface of the Application within 5 minutes
ix) Verify Admin Login with valid input data to Admin Interface of the Application after 5 minutes
x) Verify Required Elements availability of Admin Index page (After Admin Login)
xi) Verify Add Manufacturer
xii) Verify Edit Manufacturer
xiii) Verify Delete Manufacturer
xiv) Verify Add Category
xv) Verify Edit Category
xvi) Verify Delete Category
xvii) Verify Add Product
xviii) Verify Edit Product
xix) Verify Delete Product
xx) Verify Add Currency
xxi) Verify Edit Currency
xxii) Verify Delete Currency
xxiii) Verify Set a Currency a Default
xxiv) Verify Customer Reports
xxv) Verify Product Report
Etc...

11) Derive Comprehensive (All possible test cases) Test cases for User Interface