• ZenSOFT has highly competent pool of resource on Software Test Automation.
• ZenSOFT owes its success in the last three years in the area of Software Test Automation to ZenSOFT’s very own Test Automation Framework which enables it to build complex Test Automation Suites quickly. Apart from productivity it also extensively improves the maintainability and scalability of the Test Suite.
• The framework helps functional / business users to get build and execute their own customized suites at the click of a button.
• The framework can automatically execute the suite on a timely basis and deliver customized reports online or over an email.

• Feasibility
• Scope & Sizing
• Planning & Scheduling
• Test Suite Design & Framework
• Build & Execute
• Analyze & Report

Feasibility

Objective

• Study and understand the system requirements or use cases to understand the system under test.
  The major objective at this phase is to identify any technical limitations with the help of a POC in using the Functional Automation Test Tool.

Activities

• Build a Knowledge transition plan along with the client to help ZenSOFT understand the domain and application under test.
  Client will update all the required Test Cases to be considered for automation.Simultaneously all tools identified will be tested for their feasibility of usage on all the critical test scenarios in the system under test, identified by the client. ZenSOFT’s automation test engineer would analyze the result of the feasibility study and report issues if any to the business.
  ZenSOFT would also suggest workarounds on problems identified during this phase. ZenSOFT has had some outstanding success stories in suggesting and implementing workaround owing to its strong associations with the market leaders in Test automation like IBM and Mercury.

Artifacts

• Feasibility Study Report (FSR) is generated that
  1. clearly outlines the feasibility of usage of the identified tools with the system under test
  2. Knowledge Transition Plan
  3. Final List of Test Cases to be considered for automation, reviewed and signed off by Business.

Scope & Sizing

Objective

• To scope and phase the business needs identified depending on the FSR.
• To arrive at a High Level Effort Estimate using the defined scope to empower the business with critical information like deliverables, costs and timelines.

Activities

• The FSR is reviewed with the stakeholders to define the clear scope of involvement.
• List of identified activities in the FSR will be prioritized and phased as agreed by the stakeholders and ZenSOFT.
• More importantly this would also clearly define what will not be part of the scope of work. This helps in deciding clear boundaries of work.
• Using ZenSOFT’s High Level Effort Estimation technique that helps standardize the process of Effort Estimation and quickly arrive at a high level effort estimate taking into account all standard effort heads like change management, project communication, system / infrastructure dependencies etc.

Artifacts

• Scope Definition document that outlines the scope of work with the defined accountabilities.
• High Level Effort (HLE) Estimate clearly defining the phase wise estimate in man hours.

Planning & Scheduling

Objective

• To clearly outline deliverables, milestones, resource plan and timelines

Activities

• To clearly outline deliverables, milestones, resource plan and timelines
• The plan will be published to the stakeholders and the team and will be the basis for monitoring progress and reporting status to business.

Artifacts

• Project Plan would capture the following details
  1. Service Objective
  2. Project Overview
  3. Project Scope
  4. Deliverables and Sign Off
  5. Project Specific / Client Templates if any
  6. Technical Standards and Compliance
  7. Effort Estimate
  8. Project Schedule
  9. Project Organization Structure
  10. Team Structure
  11. Resource Plan
  12. Roles and Responsibilities
  13. Quality Measurement Metrics

Test Suite Design & Framework

Objective

• The major objective of this phase is to build a reusable, maintainable and scalable framework which will help improve the productivity and quality of the current test team, Design Engineers, Business Analysts and also end Business users. The above figure shows

Activities

• Explore and analyze the work flow of the application under test to come up with a modularized design which can be easily scalable.
• Quickly build isolated loosely coupled test utilities which would help initializing, creating, executing and reporting with in the Test Suite
• Test Suite Design and Architecture document.

Artifacts

• Test Suite Design and Architecture document.

Build & Execute

Objective

• The objective here is to implement the application test cases into the designed Framework

Activities

• Convert the Test Scenarios identified for automation into a designed format.
• Design test tasks depending on the test strategy.
• In this phase, individual tasks with an entire set of positive and negative Test data will be designed. This layer isolates task (test case) and data. This also enables the suite to quickly adapt to change in requirements.
• Individual tasks along with test data used to configure and build various scenarios (work flows). Change in the workflow can now be achieved by a simple configuration change.
• The Automation Test cases will be mapped to Manual Test Cases or Requirement Specification which helps in measuring the test coverage
• Test Suite Execution can be controlled at Scenario and feature/module levels. The execution interface could be easily used by developers, Test Leads, Business Analysts and End Business Users to build and execute their own custom suites.
• The Test cases will be executed and results will be captured against the test cases.

Artifacts

• Test Task design document
• Test Automation Suite

Analyze & Report

Objective

• Main objective of this phase is to analyze the Test Results and reports issues to various entities.

Activities

• The Test Automation Suite on execution will automatically send different report.
• Test Engineers would get a detailed report on the individual test cases and their execution status.
• This report will also detail the cause of failures if any.
• Business will receive dashboards which will consolidate the test status and also report trends and analysis on various execution cycles of tests. This helps the business to keep a check on the health of the application under test.
• Test Engineers would identify failed test cases, analyze the cause of failure and report the defects to the Test Lead.
• Test Lead would verify and validate the defects and their severity to the system under test and report it to the Development Team.

Artifacts

• Detailed Test Execution Report sent to the identified users.
• A separate consolidated business report
• Detailed Defect Report raising defects to developers
• Dashboard would also contain
  1. Defects per cycle of Execution
  2. Regression Defects Report
  3. Functionality wise Defect Distribution Report
  4. Severity wise Defect Distribution Report
  5. Defect Density Report