Syensqo IS - Customer Support

Page tree

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

Table of Contents


  • Testing Strategy Definition

    • Overview of Testing Strategies
    • Importance of a Defined Strategy
    • Components of a Testing Strategy

  • Defining the Testing Process

    • Key Steps in the Testing Process
    • Roles and Responsibilities
    • Entry and Exit Criteria

  • Managing Test Plans

    • Overview of Test Plans
    • How to Create and Update a Test Plan
    • Managing Changes to Test Plans

  • Test Scripts Repository

    • Defining a Test Scripts Repository
    • Organizing Test Scripts
    • Version Control for Test Scripts

Test Repository :: This will be our test case Library with following limitation ie test repo is a project level feature, so each test repository can only contain test from its projects (we cannot mix tests from multiple projects into a single repository and organize them together)

All test cases which we create end up in Test Repo by default.


Test Sets :: Is a group of tests , we can consider this to be the equivalent of a single folder inside the test repository.

Test sets are more flexible than test repository and that a test set can contain tests from multiple projects and a single test case can live in multiple test sets.

Under test sets we create All E2E , Regression tests , Test Release plans.


Following are Agreed by Dina ::

Test Repository Decison:

  • Folders - will be used to structured the repository by Application >> Process >> Test Type - this folders will contain all test scripts that will be created by BAs, QA Lead will maintain the structure, and Test Scripts cannot be cloned.




  • Test Sets - will be used to include all scripts needed for a certain release, this will be managed by QA Lead

  • Test Sets will contain the regression pack, EtE test per release, this will be managed by QA Lead






  • Test Plan - Create test plan according to Monthly Releases for INT and UAT & Prod testing i.e





  • Test Executions - Test Executions are created as children under Test Plan and will be by Release and Envoirment: INT, UAT, PROD (Sanity PROD), this will be managed by QA lead.


The BAs will need to create or update test scripts, identify if the test Script needs to be executed for a certain release by adding or updating the fix Version >> this will allow QA lead to create the Test Sets, Test Plan and Test execution.


  • Test Executions

    • Types of Test Execution
    • Monitoring Test Execution Progress
    • Handling Test Execution Failures

  • Bug Reporting

    • Guidelines for Reporting Bugs
    • Information to Include in a Bug Report
    • Bug Reporting Workflow

  • Bug Creation

    • How to Create a Bug Report
    • Common Bug Types
    • Tools for Bug Creation

  • Fixing a Bug

    • Steps in Bug Fixing
    • Coordination with Development Teams
    • Verifying the Bug Fix

  • Test Progress Reporting

    • Key Metrics for Test Progress
    • Creating Effective Test Reports
    • Tools for Reporting Test Progress

The best way to get IT support is to use the new Service One Platform.