40 – Selenium Project

Selenium Class 40 – Selenium Project

Functional Test Automation using Selenium,

Application (AUT): gcrShop Online Shopping web portal

i) Admin Interface: For Application Master Data and Maintenance…
(http://www.gcrit.com/build3/admin/)

ii) User Interface: For conducting business operations
(http://www.gcrit.com/build3/)

Selenium Project
1) Project Information
2) Project Description
3) Stake Holders of the Project
4) Interfaces of the Project/AUT
5) Features to be tested in Admin Interface
6) Features to be tested in User Interface
8) 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 Cases for Admin Interface
11) Derive Comprehensive (All Possible) Test Cases for User Interface
………………………………..
Steps:

• Understanding the AUT (Application Under Test) Requirements

Note: This is common task for Software Testing (Manual Testing or Automated Testing)

Test Level: System Testing
Test Type: Functional Testing

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: Business to Customer (B2C)
Application: Online Shopping
Application Environment: LAMP(Linux, Apache, MySQL, PHP)
Type of the Application: Public Web Application (Internet Application)

2) Project Description:

In this Software Application we have 2 Interfaces,
1) Admin Interface/Server side Interface – (Application Master Data, and Maintenance…by Admin User/s of the Organization)

2) User Interface / Client Interface: Conducting specified Business Operations

Online Shopping Application,

1st Type: Vendor develops their own online shopping portal to sell their products

2nd Type: Some third party develops Online Shopping to sell and buy products

Note: Our Application is 2nd type…

Admin Interface:

In Admin Interface, First Manufacturer Registration, Add Category, Add product, Add Currency….

Edit Manufacturer , Edit Category, Edit product, and Edit Currency….

Delete Manufacturer , Delete Category, Delete Product, and Delete Currency….

Reports, Customer wise Reports, Product wise Reports etc…
…………………………….
User Interface:

In User Interface, Portal Developer provides interface between Manufacturers and Customers,

Manufacturers place/show their products information and sell…

Customers view Products, Search products, Register, Buy Products, and Track Orders
……………………………………….
Users of the Application:

i) Admin Interface:
Admin, Manufacturers, Financial Service provider, Distributor, Courier Service provider etc…

ii) User Interface:
Guest User, Registered User…

http://www.gcrit.com/build3/admin/

http: It is Protocol
www- World wide web
gcrit.com – Domain

/build3/- Folder
/admin/-Sub Folder

https://www.sulekha.com/hyderabad -Hyderabad is Folder for sulekha.com domain
http://telugu.greatandhra.com/- telugu is the sub-domain of greatandhra.com

3) 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…

4) Interfaces of the Project/AUT

Three Interfaces of Software Application,
i) Admin Interface
ii) User Interface
iii) Database Interface

i) Admin Interface:
http://www.gcrit.com/build3/admin/

Username: admin
Password: admin@123

2) User Interface
http://www.gcrit.com/build3/

5) Features to be Tested in Admin Interface

i)Launch Application
ii) Login to Admin Interface of the Application
iii) Redirecting Operation from Admin to User Interface
iv) Add /Edit/Delete Manufacturer
v) Add /Edit/Delete Category
vi) Add /Edit/Delete Product
vii) Add /Edit/Delete/Set as Default Currency
viii) Reports (User, product etc…)

6) Features to be tested in user Interface

i) Launch Application
ii) View Product/s
iii) Search Products/s
iv) Advanced Search
v) Customer Registration
vi) Customer Login
vii) Buy Product/s (Login, Choose product/s, Update Quantity, Delete Product/s, Change Details, Select Payment Option, Checkout…)
viii) Track Order status…

Business Flow/s of the User Interface

i) Launch Application + View Products + Search Product/s….
ii) Launch Application + Registration + Login…
iii) Launch Application + Login + Buy product/s
iv) Launch Application + View Products + Buy Product/s + Login /Register…
v) Launch Application + Login + Buy product/s (Choose product/s, Choose Quantity, Change Details, Select Payment Option, Checkout…) Etc…

7) Test Requirements, Test scenarios, Test Cases, and Test Data…

Business Requirements (BRS…)
Software Requirements (SRS…)
Test Requirements…
Test Scenarios(Positive and Negative…)
Test Cases (Positive and Negative…)
* Collect Test Data…
Note: Test Data is not required for all Test cases…

Soft Requirements / Test Requirements
i) Functional Requirements
ii) Non Functional Requirements
Performance Requirements
Usability Requirements
Reliability Requirements etc…

Functional Requirement: Admin User Login to gcrShop Application’s Admin Interface…

Test Scenarios:

i) Admin Login with valid username and valid password (Positive Test Scenario)
ii) Admin Login with invalid username and valid password (Negative Test Scenario)
iii) Admin Login with valid username and invalid password (Negative Test Scenario)
iv) Admin Login with invalid username and invalid password (Negative Test Scenario)
v) Admin Login with blank username and blank password (Negative Test Scenario)
etc…

Test Case:

1) Test Case ID: TC_Adm_001
2) Test Case Name/Description: Verify Admin Login to the Application (with valid test data)
3) Test Suite ID: TS_Adm_01
4) Priority: P0
5) Pre condition: None
6) Steps to be Executed:
i) Launch Browser
ii) Enter valid URL
iii) Enter valid Username
iv) Enter valid Password
v) Click Default/Login Button
7) Test Data:
i) Username: admin
ii) Password:admin@123
Or
Ref: input.xlsx…
8) Post Condition: Get Index page of the Application
9) Software & Hardware: Hardware Configuration, Windows 10 OS etc…
10) Expected Result: Index Page of the Application
11) Actual Result:
12) Status/Test Result:
13) Comments…
……………………………………..

Performance Requirement: Admin Login to the Application with 1000 concurrent users in 5 seconds…

Usability Requirement: Verify Field Alignments and Font Sizes in Admin Login Page

Reliability Requirement: Redirecting from Admin Interface to User Interface, 20 times…

8) Derive Smoke Test Scenarios from Admin Interface:

i) Launch Application (includes Launch browser…)
ii) Verify Required Elements availability in Login Page/Homepage
iii) Verify Admin Login with valid username and valid password
iv) Verify Required Elements availability in Index Page
v) Add Manufacturer
vi) Add Category
vii) Add Product
viii) Add Currency etc…
…………………………………………………………