Audit of the manual testing process

Provided services

Manual Testing

Client

A software company.

Product

An application for the automation of staff work time logging.

Business challenge

A manual testing team had been working on the project for the creation of the IT product for quite a long time. However, at a certain point the customer decided that the testing processes on the project needed to be improved. He wanted to assess the strengths and weaknesses of the quality assurance process, see if best practices were used, and see how efficiently the company’s resources were being spent. Therefore, he decided to involve JazzTeam to conduct a comprehensive audit and eliminate problems with manual testing on his project.

Technological features of the project

  • Missing test documentation (test cases, test plan).
  • Strong dependence on a certain team member, as only he had unique knowledge about the product operation.
Audit of the manual testing process

Approaches and solutions

  • Analysis of test cases.JazzTeam specialists started the audit by evaluating the test cases prepared by the customer’s team. During the analysis, it was found that the cases were inconsistent with the current state of the product. Therefore, it was necessary to create new test cases, delete outdated ones, as well as correct and supplement the existing ones. In addition, parts of the application that were not covered with test cases were found. As a result of the audit, our team came to the conclusion that it was possible to optimize the test cases (structure and approaches). This made it possible to reduce their number by 30%, while preserving the product coverage.
  • Testing the application. Functional, regression, and unit testing of the system was carried out. As a result, 12 major, 4 minor, and 5 critical bugs were found, and their elimination was taken under the control of JazzTeam specialists.
  • Creating a single test library. Our specialists made a proposal to systematize and structure the cases. This allowed checking in the process of making changes only those parts of the functionality that really needed to be evaluated.
  • Application of test design techniques. In the process, the concept of boundary values was applied because in order to ensure the quality of the system, it was necessary to test the work of a large number of different forms.
  • Optimization of the role model testing process. A single document was created that defined the rules for testing roles in the application. This made it possible to save a large amount of time and carry out this type of testing before each release.
  • Vulnerability detection. OWASP ZAP automated utility was used to detect vulnerabilities in the system. A number of vulnerabilities were detected in the application, including an incorrect cross-domain configuration and the absence of tokens against CSRF attacks. Each vulnerability was further thoroughly analyzed and, if necessary, remedied.
  • Regular synchronization with the customer’s testing team. During the audit, constant interaction with the customer’s testing team was established. Problems and solutions were discussed together. JazzTeam’s manager supervised all the improvement processes, which made it possible to achieve good results in a short time. By actively participating in the testing process according to best practices, the customer’s specialists were able to significantly boost their professional competence.

Results and achievements

  • An audit was conducted on the project, and the necessary improvements were implemented: the testing process was optimized, vulnerabilities and bugs were eliminated.
  • A unified application testing system was created, which made it possible to reduce the time spent on quality assurance and save the customer’s resources.
  • The professional level of the customer’s QA team significantly increased.
  • All necessary test documentation was prepared and structured.

Technologies used

tech picture
OWASP ZAP
tech picture
Jira
tech picture
Postman
tech picture
Chrome DevTools

    Contact Us

    What happens next?
    1
    Leave your project request. We will contact you and schedule a call.
    2
    Signing of the NDA to ensure the project info confidentiality.
    3
    Negotiation of your request and the required services.
    4
    Team forming, coordination of workstages.
    5
    Contract signing and project start.