Selenium Lesson 37: Selenium Live Project Part-2|Selenium Tutorial|G C Reddy|

Software Testing Live Project explanation, Automated Testing using Selenium WebDriver, Java and TestNG Framework, Undersatnding Software Project Requirements and Select Test Cases for Automated Testing using Selenium Webdriver.
Software Testing Project Information, Interface of the Project, Software Testing Project Description, Stake holders of the project, Features to be tested, derive smoke Test scenarios and derive comprehensive Test scenarios.
Automate Manual Test Cases using Selenium WebDriver, Java programming, TestNG Testing Framework, Maven and Jenkins.

[gcreddy]

Class Notes:
Selenium Class 37: Selenium Project Part-2

ii) Project Description

In this Software Application we have two interfaces (GUI),
a) Admin Interface / Server side Interface
(Maintenance of the Application...)

b) User Interface /Client side interface
(Conducting specified Business operations)

Online Shopping Application,

1st Type: Vendor /Manufacturer develops their own application to sell products
2nd Type: Third Party develops Online Shopping application to sell and buy products
Note: Our Application is 2nd type application

a) Admin Interface:
> Login to Application Admin Interface
> Manufacturer Registration, Add Category, Add Product, Add Currency...
> Edit Manufacturer, Category, Product, Currency...
> Delete Manufacturer, Category, Product, Currency....
> Set default currency...
> Reports, Customer wise Reports, Product wise Reports

b) User Interface

In User Interface, Portal developer provides interface between Manufacturers and customers
> Manufacturers enter their Products information in admin interface and sell those products using user interface
> Customers view products, search for products, buy products, and track order stratus

Users of the Application

a) Admin Interface
Admin, Manufactures, Financial service providers, Distributors, Courier service providers etc...

b) User Interface
Guest User, Registered Users,


http - It is a Protocol
www - World wide web
gcrit.com - Domain
/build3/ - Folder
/admin/ - Sub Folder

telugu.greatandhra.com - "telugu" is a sub domain of greatandhra.com

iii) Stake holders of the project

An individual, group, organization, who may effect, be affected by or perceive itself to be effected by
a decision or activity or outcome of a product

> Project Leader/Project manager
> Senior management
> Software developers
> Software Testers
> Business Analyst
> Technical support people
> Contractors
> Consultants (ex: SME....)
etc...

iv) Features to be Tested in Admin Interface

a) Launch Application, Redirect to User Interface from Admin Interface (before login and after login)
b) Login to Admin Interface of the Application
c) Add/Edit/Delete Manufacturer
d) Add/Edit/Delete Category
e) Add/Edit/Delete Product
f) Add/Edit/Delete/Set Default Currency
g) Reports

v) Features to be Tested in User Interface

a) Launch Application
b) View Product/s
c) Search product/s
d) Advanced Search
e) Customer Registration
f) Customer Login
g) Buy Product/s (Login, Choose Product/s, Update Quantity, Delete Product/s, Change Details,
Select payment option, checkout)
h) Track Order Status
etc...

Business Flow/s of the User Interface

i) Lunch Application + View Products + Search Products + Close Application
ii) Lunch Application + Registration + View products + Close Application
iii) Lunch Application View products + Registration + Close Application
iv) Lunch Application View products + Registration + Login + Buy Product/s + Close Application
v) Launch Application + Login + View Product/s + Buy Product/s + Close Application
Buy Product/s - Choose product/s, Choose Quantity, Remove Product/s, Change Details, Select payment option, Checkout)
vi) Launch Application + View Product/s + Buy Product/s + Login + checkout+ Close Application
vii) Launch Application + View Product/s + Buy Product/s + Register +checkout+ Close Application
etc...

vi) Test Requirements, Test Scenarios, Test Cases and Test Data

Business Requirements (BRS)
Software Requirements (SRS)
Test Requirements
Test Scenarios (Positive and Negative scenarios)
Test Cases
Test Data

Software Requirements/ Test Requirements
i) Functional Requirements
ii) Non Functional Requirements
Performance Requirements
Usability Requirements
Reliability Requirements
Etc...

1) Load Testing, Stress Testing, Spike Testing, Endurance Testing etc..are subsets of Performance Testing
2) Security Testing, Interoperability Testing are subsets of Functional Testing
3) Database Testing is subset of Functional Testing and also subset of Performance Testing

Functional Requirement: Admin user Login to gcrShop Application

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

Test Case:
1) Test Case ID: TC_Adm_001
2) Test Case Name /Description: Verify Admin Login to the Application with valid input
3) Test Suite ID: TS_Adm_01
4) Priority: P0
5) Precondition: None
6) Steps to be Executed:
i) Launch browser
ii) Enter valid url (navigate to admin interface)
iii) Enter valid Username
iv) Enter valid password
v) Click default (Login) button
7) Test Data/Input:
i) Username: admin
8) Post Condition: Application index page
9) Test Environment (Software & Hardware): hardware configuration and Software details
10) Expected Result: Index Page of the Application
11) Actual Result: (* After Test case execution)
12) Status/Test Result: (* After Test case execution)
13) Comments:

> Performance Test Requirement: user Login to An Application with 2000 concurrent users
in 5 seconds

> Usability Test Requirement: Verify Field Alignments and Font sizes in Admin Login Home Page

> Reliability Test Requirement: Redirect from Admin interface to User Interface for 30 times

vii) Derive Admin Interface Smoke Test Scenarios

i) Launch the Application with valid url
ii) Verify required elements availability in Admin home page
iii) Verify Admin Login with valid data
iv) Verify required elements availability in Index page
v) Add Manufacturer
vi) Add Category
vii) Add Product
viii) Add Currency
etc..

viii) Derive User Interface Smoke Test Scenarios

i) Lunch Application with valid url
ii) Verify important elements/fields availability in the home page
iii) Verify "Customer Registration" with valid data
iv) verify "Customer Login" with valid data
v) Add products to shopping cart
vi) verify checkout process
vii) Verify "Track Customer Order" Status
etc...

[monicatiwari]

Sir can u please teach us ui path +gcreddy