White Papers & Articles

Explore our ideas, development experience and industry knowledge

A Single Quality Assurance Specialist Can Transform the Entire Development Process

A Single Quality Assurance Specialist Can Transform the Entire Development Process

Adding a Quality Assurance specialist allows you to better manage your project, but it also presents its own set of problems. What common issues do organizations (and QAs) face when testing their project results? The following case study describes the management process of large projects when a QA specialist is introduced in the middle of the project development life cycle. Emphasis is placed on main problems encountered in such situations and the solutions that were applied in an existing Intetics project.

Summary

Adding a Quality Assurance specialist allows you to better manage your project, but it also presents its own set of problems. What common issues do organizations (and QAs) face when testing their project results? The following case study describes the management process of large projects when a QA specialist is introduced in the middle of the project development life cycle. Emphasis is placed on main problems encountered in such situations and the solutions that were applied in an existing Intetics project.

Introduction

The main objective of the project was to find a BI solution that would maintain a large trading network database.

The development team created and maintained the following set of programs and services:

  • 30 Web applications, each containing at least two language locales
  • 5 self-recording protocols for exchanging data with customers
  • Web Service comprising of more than 50 methods

Under these conditions there was only one QA specialist on the team who tested the results of the project.

The main problems at the start of testing

The following were the main problems encountered at the start of testing. In general, there was a complete lack of organized working documentation, as well as lack of functionality testing:

  • 1. Arrangement of working documentation:
    • a. Lack of Project Documentation
    • b. Lack of Centralized Document Storage
    • c. Complete lack of test documentation
  • 2. Gaps in Functionality Testing :
    • a. Large volumes of regression testing
    • b. Complete lack of testing automation
    • c. Unchecked non-functional requirements

Solution to problems

  • Arrangement of working documentation
  • Functional Testing
    • Working with test cases
    • Manual Testing
    • Testing automation

Resulting Improvements

  • The application is covered with tests cases at all levels
  • Project documentation is always up to date
  • Regression testing time reduced to 4 hours
  • Testing is no longer “dumped” on the end of iteration
  • The whole team is involved in the testing process
  • Number of production customers defects reduced from 5 per week to 1 in 2-3 months
  • Free up time for checking non-functional requirements


Download detailed version of case-study to learn about the management process of large projects when a QA specialist is introduced in the middle of the project development life cycle

White Paper

Full Version Download
  • * Name:
  • * Company:
  • * Email:
  • * Phone:
  • * Position:
  • Capture: captcha
  • Cancel


Do You have any questions? Feel free to ask us Contact