0% found this document useful (0 votes)
161 views2 pages

Capstone Project Demowebshop Tricentis

The project focuses on automating the testing of the Demowebshop.tricentis.com website using Selenium and Cucumber for BDD. Key functionalities such as UI testing, user registration, and order placement will be verified through an automated test suite, with integration of tools like Maven, Jenkins, and TestNG. The implementation will follow best practices including the Page Object Model, data-driven testing, and detailed reporting of test results.

Uploaded by

Nilesh Patel
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
161 views2 pages

Capstone Project Demowebshop Tricentis

The project focuses on automating the testing of the Demowebshop.tricentis.com website using Selenium and Cucumber for BDD. Key functionalities such as UI testing, user registration, and order placement will be verified through an automated test suite, with integration of tools like Maven, Jenkins, and TestNG. The implementation will follow best practices including the Page Object Model, data-driven testing, and detailed reporting of test results.

Uploaded by

Nilesh Patel
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

Capstone Project: Automated Testing of Demowebshop.tricentis.

com

URL: http://demowebshop.tricentis.com

Project Overview:

This project aims to automate the testing of various functionalities of the


Demowebshop.tricentis.com website using Selenium for UI testing by using Cucumber for
Behavior-Driven Development (BDD with POM..

1. Automated UI Testing with Selenium

 Task: Develop an automated test suite to verify key functionalities on


Demowebshop.tricentis.com using Selenium.
 Test Environment Setup:
o Set up Selenium WebDriver with a test framework like TestNG or Junit.
o Implement BDD with POM concepts.
o Integrate the project with Maven.
o Implement Cross-browser testing with Chrome, FireFox and Edge browser.
o Set up CI/CD using Jenkins or GitLab CI to automate the test execution.
 Automated Test Cases:
o Home Page:
 Verify the display of major sections like Top Offers, Recommended for
You, and search bar functionality.
o Search Functionality:
 Automate searching for products, filtering results by category, price, and
ratings.
o Product Details Page:
 Validate the product title, description, price, images, and availability.
 Test adding products to the wishlist and cart.
o Shopping Cart:
 Automate adding items to the cart, removing them, updating quantities,
and proceeding to checkout.
o User Registration and Login:
 Automate the user registration process, login, and password recovery.
o Order Placement:
 Test the entire flow from adding items to the cart to completing a
purchase.
 Reporting:
o Generate detailed test execution reports using Extent / Allure Report.

Following concept should be included:

a. Web driver
b. testng
c. Maven
d. BDD with Cucumber
e. Jenkins
f. GIT
g. Automation Framework

Design considerations:

a. POM (Page object model) pattern in the hybrid framework


b. Testng Implementation, Proper testng concepts and XML to run the project
c. Should have implemented reusable functional separately to improve more readability
d. Multi browser execution. Should have handled at least two browsers (Firefox and
IE/Chrome)
e. Data driven concept – Input data should be imported from an external excel sheet (Ex:
Using Apache POI libraries in case of java) or Properties file or Flat file
f. Handled exceptions with exception handling & error messages
g. Should have used relative xpath wherever necessary
h. Check code is syntactically correct and executes end to end successfully
i. Use ID or Name locator instead of Xpath
j. Implementation with BDD with Cucumber along with Maven
k. Screen shots for the failed steps to be created
l. Extent/Allur reports to be generated

Best practices:

1. If else condition is written to control the test script flow


2. Code for taking screen shot
3. Coding standard to be followed with proper comments
4. All scripts/business components/test results should be in respective folder
5. Should include page synchronization timers
6. Script to run end to end without any issue
7. Assertion and exception handling concept.

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy