Divya Ramamurthy

TEST STRATEGY DOCUMENT By Divya Ramamurthy PROJECT: SPREE DEMO SITE CONTENTS: 1. PRODUCT TEST OVERVIEW 2. ARCHITECTURAL VIEW OF PROJECT 3. TYPES OF TESTING TO BE PERFORMED 4. TESTING TOOLS USED 5. STORY LIFECYCLE 6. DEFECT LIFE CYCLE 7. CODE FLOW TO PRODUCTION 1 1.PROJECT TEST OVERVIEW Spree Demo Site is an ecommerce website (online portal), which facilitates online transactions of goods and services through means of the transfer of information and funds over the internet 1.1 Application’s Functionality There four important elements in its structure, and they are: ● Main Pages – Homepage, Product page, Special Offers, About Us page, Sitemap pages, Privacy Policy page, Press Releases page, etc. ● Category / Product Type Pages – The product page consists of options such as product size, color, and type. There is a sorting feature to filter out products based on price, model, size, etc. There is also the “Add to Cart” or “Add to Wishlist” feature present in the category pages. ● Product Description Page – Consists of the product title, description, product images, related products, Add to Cart feature, Product comparison, additional product info, etc. ● Shopping Cart – Products list view, removing the product from the list, cash on delivery option, Select delivery option, card payment, pay now option, etc. 1.2 Application Workflow ● Login and Signup options ● Search functionality ● Product review posting feature 2 ● Sorting feature ● Applying filters for choosing the desired product(s) ● Add/remove functionality in the shopping cart ● Check out process ● Order number and invoice generation ● Payment gateway and payment processing 1.3 Payment Gateway Functionality Require conduct multiple tests to ensure it functions properly and provides security while doing online transactions. 1.4 Performing Security and Vulnerability Assessments Since e-commerce applications hold valuable information (customer’s personal and banking data) it is required to conduct security testing to check for security and vulnerability issues. 1.5 Checking Compatibility with Web Browsers Ensure application to work on all types of web browsers such as Google Chrome, Firefox, Opera, Internet Explorer, Safari, etc. 1.6 Testing for Mobile Responsiveness Test the responsive design of your application in mobile devices of various screen sizes. 1.7 Checking Performance and SEO-related Things Check the performance of your website. Test whether SEO strategies such as title tags, meta descriptions, URL structure, image alt tags, etc are implemented correctly. 3 1.8 Other Common Things to be Tested They include website content, webpage format, website accessibility, cookies, social buttons, adding/deleting content, removing/adding links, web standards, analytics, and making changes to shipping settings. 1.9 Social Media Integration Make sure that social media integration is aligned with website architecture and workflow. 2.ARCHITECTURE VIEW OF PROJECT: 4 3.TYPES OF TESTING TO BE PERFORMED ● Functional Testing - Manual and Automation ● Usability testing - Manual ● Database Testing - Manual ● Security Testing - Manual ● Performance Testing - Automation ● Acceptance Testing - Manual 4. TESTING TOOLS USED: ● Automation Tool for website UI functional tests - Selenium Webdriver ● Performance tests - Jmeter 5 5. STORY LIFECYCLE: 6 6. DEFECT LIFE CYCLE 7 7. CODE FLOW TO PRODUCTION 8