Selenium Tutorial For Beginners 37|Selenium Live Project|G C Reddy|

Automated Testing or Test Automation using Selenium, Software Project Information, Project Description, Stake Holder of the Project, Interfaces of the project, Features to be tested in Admin Interface, Features to be tested in User Interface, Test Requirements, Test Scenarios, and Test Cases, Derive Smoke Test Scenarios for Admin Interface, Derive Smoke Test Scenarios for User Interface, Derive Comprehensive(All Possible) Test Scenarios for Admin Interface, and Derive Comprehensive(All Possible) Test Scenarios for User Interface.

[gcreddy]

Class Notes:
Selenium Class 37: Selenium Project

Automated Testing/Test Automation using Selenium,

AUT (Application Under Test): gcrShop Online Shopping Portal

i) Admin Interface: For Application Maintenance...

ii) User Interface: For conducting specified Business Operations

Selenium Project
1) Project Information
2) Project description
3) Stake Holder of the Project
4) Interfaces of the project
5) Features to be tested in Admin Interface
6) Features to be tested in User Interface
7) Test Requirements, Test Scenarios, and Test Cases
8) Derive Smoke Test Scenarios for Admin Interface
9) Derive Smoke Test Scenarios for User Interface
10) Derive Comprehensive (All Possible) Test Scenarios for Admin Interface
11) Derive Comprehensive (All Possible) Test Scenarios for User Interface

Test Execution in STLC/Software Test Process:
Levels of Test Execution:
Smoke Testing...
Comprehensive Testing...
Defect Reporting and Tracking

Sanity Testing...
Regression Testing Cycle 1(Re-Testing & Regression)
Defect Reporting and Tracking

Sanity Testing...
Regression Testing Cycle 2(Re-Testing & Regression)
Defect Reporting and Tracking

Sanity Testing...
Regression Testing Cycle 3(Re-Testing & Regression)
Defect Reporting and Tracking
.
.
Final Regression
Comprehensive Testing,
Test Case1, -Passed
Test Case2, -Passed
Test Case3, -Failed
Test Case4,

Regression
Test Case2

Re-Testing
Test Case3, -Failed

Re & Regression...
Test Case2 and Test Case3

Steps:
> Understanding the AUT Requirements,

Test Level: System Testing
Test Type: Functional Testing...
Functionality Testing, Database Testing etc...

1) Project Information

Domain: Ecommerce

Note: Domain means an Area, Software Development point of view, domain means
Project Business Area,

ERP,
BFSI,
Banking,
Insurance,
Telecom,
Healthcare,
Ecommerce,
Travel,
Retail Market,
Others (Games, Antivirus etc...)

Sub Domain: B2C (Business to Customer)
B2B,
C2C-
C2B
Application: Online Shopping
Application Environment: LAMP (Linux, Apache, MySQL, and PHP)
Type of the Application: Public Web Application (Internet Application)

2) Project Description

In this Software Application we have 2 important Interfaces,
i) Admin Interface/Server side Interface-
Application Master Data, User management, and Maintenance....)

ii) User Interface/Clint side Interface
Conducting specified Business Operations...

Online Shopping Applications are 2 types,

1st Type: Vendor develops their own online shopping application to sell their products only
2nd Type: Some third party develops online shopping application to sell products

Our Application is Third Party Application

Admin Interface:
Admin Registration/Login, Manufacturer Registration, Edit Manufacturer, delete Manufacturer,
Add Category, edit Category, Delete Category, Add Product, Edit product, Delete
product, Add Currency, Edit Currency, Delete Currency., Set default Currency, Generate Reports

User Interface:
Customer Registration, View Products, Search products, Advance Search, Buy Products,
Etc...

3) Stake Holder of the Project
An individual or group or organization, who may effect or be affected by
a decision or activity or outcome of a project....

i) Project Leader
ii) Senior Management,
iii) Project Team Members Developers, BA, tech Support, Testers etc.,
iv) Project Customer
v) Sub Contractors, Consultants etc...

4) Interfaces of the project
i) Admin Interface
Username: admin

ii) User Interface

iii) Database Interface


http-Protocol
www-world wide web
gcrit.com- web domain/web Address
build3 -Folder
Admin- Sub folder
login.php- Web Page

english - Sub Domain
tupaki.com -Domain

SubDomain.Domain
Domain/Folder

5) Features to be tested in Admin Interface

New Application - Features to be tested only,
New version of existing software - Features to be tested only and Features not to be tested

i) Admin Login
ii) Redirecting from Admin to User (Before and After Login)
iii) Add/Edit/delete Manufacturer...
iv) New /Edit /Delete Category
v) New /Edit /Delete Product
vi) New /Edit /Set As Default / Delete Currency
vii) Reports (Product, Customer)
viii) Reviews
ix) Logoff Etc...

6) Features to be tested in User Interface

i) Customer Registration
ii) Customer Login
iii) Search products
iv) Advanced Search
v) Shopping Cart
vi) Check Out
vii) Logoff etc....

Business Flows:
i) Lunch Application + View Products + Close Application
ii) Lunch Application + Search Products + Close Application
iii) Lunch Application + View Products + Advanced Search + Close Application
iv) Lunch Application + Registration + Close Application
v) Lunch Application + Registration + Login + Close Application
vi) Lunch Application + Login + Buy Product + Close Application
vii) Lunch Application + Buy Product + Registration + Close Application
etc...

7) Test Requirements, Test Scenarios, and Test Cases

Business Requirement
Software Requirement
Test Requirement

Types of Requirements (Functional and Non-Functional Requirements)
Functional Test Requirement
Performance Test Requirement
Usability Test Requirement etc....
Example: Functional Test Requirement
Admin Login to Application Admin Interface

Example: Performance Test Requirement
1000 Concurrent Users Login within 5 seconds

Example: Usability Test Requirement
Alignment, Sizes of Elements in Admin Login Functionality

Test Requirement: Admin Login to Application Admin Interface
Test Scenarios:
Positive and Negative Scenarios)

Scenario 1: Admin Login with Valid Username and Valid Password

Scenario 2: Admin Login with Valid Username and Invalid Password
Scenario 3: Admin Login with Invalid Username and Valid Password
Scenario 4: Admin Login with Invalid Username and Invalid Password
Scenario 5: Admin Login with Valid Username and Blank Password
Scenario 6: Admin Login with Blank Username and Valid Password
Scenario 7: Admin Login with Blank Username and Blank Password

Admin Login with Valid Username and Valid Password
Test Case Documentation:

Test Case ID: gcrShop_Ad_001

Test Case Name: Verify Admin Login Functionality

Test Suite ID: Admin_001

Priority: P0

Test Steps:
i) Launch Browser
ii) Navigate to gcrShop Admin Interface with Valid URL
iii) Enter Valid Username
iv) Enter valid Password
v) Submit/Click Login Button

Test Data:
i) Username: admin

Pre-Condition: None
Post Condition: Admin Interface Index Page

Expected Result: Admin Interface Index Page

Actual Result:

Test Result: Pass/Fail
Comments:

Note: We fill maximum Test Case Fields before the Test Case execution, but we fill
some fields like Actual Result, Test Results, and Comments after the Test Case execution only