Test Strategy Document - Search DPT

DARCI

Document Details

• Introduction
• Planning and Strategy
  • Scope of Work
  • Dependencies and Constrains
  • Testing Concern
  • Test Schedule
  • Test Approach Strategy
    • Functional Testing
      • Unit Testing
      • Integration Testing
      • Sanity Testing
    • Non-Functional Testing
      • Internationalization testing
      • localization testing
      • performance testing
  • Test Tools Strategy
    • Click up : for Create Test Case
    • Rollbar
    • UI Testing: Chrome Browser
    • Mobile Testing: Android and IOS devices
  • Test Data Strategy
  • Test Environment
• Test Deliverables
  • Test Case Execution
  • Issue Management

Introduction

The purpose is to create an understanding Feature Released (Search people/date/time) of the overall targets, approach, tools, and timing of test activities to be done. The purpose is to create a comprehensive testing.

Planning and Strategy

Scope of Work

List any Boundaries or Limitation Product / Data scope when doing testing activity for Search DPT

• Testing Data: updated restaurant, package, inventory from admin dashboard
• Search 2.0
• Home Page
• Query Param from home page
• Select Restaurant and End To end Flow reservation

Dependencies and Constrains

Dependencies

List any dependencies identified during the development of this test strategy that may effect its successful execution if those dependencies are not honored. Typically these dependencies relate to activities on the critical path that are prerequisites to current feature activities

Constrains

List any constraints identified during the development that may affect its successful execution if those constraints are not honored. Typically these constraints relate to activities on the critical path that are post-requisites to one or more current feature activities.

Testing Concern

• This testing approach will be conducted on 2 method
  1. Manual Testing Desktop, Android, IOS, Mobile View
  2. Automation Testing for Desktop Platform (Conditional)

Test Schedule

Functional Testing

• Unit Testing
  • Implemented by Developer
  • Validated by performing code coverage
• Integration Testing
  • Performed by QA Engineer (Manual/ Automate)
  • Bottom-up Integration Testing: s a strategy in which the lower level modules area tested first.
• Regression Testing
  • Performed by QA (manually/automated)
• Sanity Testing
  • Performed by QA

Non Functional Testing

• Compatibility testing or Cross Browser Testing
• Performance Testing ( Load test, Stress Test )
  • Performed by Test Architect Speed – Determines whether the application responds quickly Scalability – Determines the maximum user load the software application can handle. Stability – Determines if the application is stable under varying load
• Internationalization testing
  • to ensure Eng version on web running well not broken the UI e.g date/time formatting, number formatting, currency formatting, address formatting, keyboard shortcut, hardcode string
• Localization testing
  • to ensure Thailand version on web running well not broken the UI e.g date/time formatting, number formatting, currency formatting, address formatting, keyboard shortcut, hardcode string

Test Data Strategy

• Fetching Data to HH-Ballbot or HH-Engineering or Production
• Data Validation:

  •   *   Check search result restaurant for the inventory and availability with data restaurant on Admin dashboard
    

    • Check number search result restaurant

Test Environment

• Environment Staging Feature Branch
• Environment Staging
• Environment Production

Issue Management (Report from QA)

use filter by tag : example (bug_development)