QA Consulting and Change Management for Enterprise Resource Management Product

checklist
  • Duration: 1 year
  • Industries: Supply Chain, Inventory & Order Management
  • Services: Test Automation Services; Manual Testing Services; IT Consulting; CI/CD Implementation & Modernization. DevOps Services
  • Software Categories and Types: ERP/CRM Systems
  • IT Architecture Paradigms and Approaches: Software Frameworks Development; Object-Oriented Programming (OOP)
  • Technical Expertise: Test Automation
  • DevOps Expertise: CI/CD Basics; CI/CD Advanced
  • Technologies: REST; WebDriverJS; Data Bases; Node.JS; Project Management, Collaboration and Bug Tracking; IntelliJ IDEA; Git; CI/CD Automation Servers; Jenkins; Apache Log4j; TestLink; Frontend; Test Management Tools; Selenium WebDriver; MindManager; Java; Redmine; Testing Frameworks; JavaScript; JavaScript Frameworks; NetCat; JVM Languages; IDE; Scala; Backend; Vue.js; Mocha; Cucumber; PostgreSQL; JavaScript Libraries; Various Editors; Selenium-Js; Standards and Protocols; Test Automation; faker.js; Test Automation; Source Code Management (SCM); Chai; CI/CD and DevOps; Languages, Protocols, APIs, Network Tools; Network Tools; Axios; Software Engineering and Management Tools; Confluence; HTTP/HTTPS; Java Libraries; Logging Libraries; Moment.js
project-team
  • Team size (3):
  • 1 Project Manager
  • 2 QA Automation

Provided services

Test Automation Services, Manual Testing Services, IT Consulting, CI/CD Implementation & Modernization. DevOps Services

Client

Rightstep is a consulting and IT company that focuses exclusively on solving problems in planning and managing production and supply. The company has over 20 years’ experience and extensive knowledge of both manufacturing and information technology. It has successful experience in the installation and system implementation in numerous industrial plants.

Product

A fast-growing ERP system for accounting and cost planning at large manufacturing enterprises in the field of mechanical engineering.

The SPM (“Lean Supply Chain Management ERP”) of Rightstep is a web application designed to manage the production and logistics chains (internal and external) of industrial enterprises. It supports both Western and Eastern industrial models, including distributed production and cooperative interaction. Allows to build PS (Production Systems) based on concepts: MRP-II (structure of plans and objects), SCM (planning methods, optimization and chain management), Lean (pulling, kanban, visualization), TOC (planning and prioritization), APS (synchronized optimized planning of the production and logistic chain), monitoring through the “proportionality chart”), etc.

The SPM includes the specifics of modern aerospace industries (long cycles, cooperation), production of special vehicles (configuration), complex instrumentation (multi-item and multiple-production), shipbuilding (long cycles, parallel design-production-assembly, a huge number of components), machine tool industry and industrial equipment production. It is also confidently implemented and applied in relatively small (tens/hundreds of people) growing enterprises, allowing evolutionary development without changing the platform.

Challenge

The functionality of the IT solution constantly changes, but the client does not have enough resources for testing. The quality assurance process is not established; the project does not have the necessary specialists. Bugs are fixed only in the product lifecycle late stage as part of acceptance testing. It is too expensive for the customer and can negatively affect their reputation. The team is unable to independently ensure the high quality of the system by the date of delivery to the end customer.

The client expected our team to be actively involved in organizing and configuring testing processes, formalizing procedures and proposals, and implementing a testing culture. They also expected us to share knowledge and adopt best practices in test automation. This was critical to ensuring the quality and effectiveness of the product development process.

The client required a detailed phased transformation plan with timelines for each phase before we could begin the project. Once the plan was approved, we began the transformation process.

Project Context

Before our team started the project, the client did not have a structured system testing process. This meant that the quality assurance process for the developed product was not organized or systematized.

Need help

Solution

We began transformations with the development of a detailed automated testing plan for the system and its subsequent implementation on the project. The plan involved the creation and implementation of over 60 integration tests and 158 smoke and regression tests. This approach to testing ensured the reliability of the product’s functionality and allowed us to quickly identify and resolve potential problems.

On the client side, we implemented a Continuous Integration (CI) system to automate the process of code integration and testing. This involved setting up Jenkins and TestLink servers and developing a custom plugin to seamlessly integrate test results from Jenkins into TestLink. This has streamlined testing workflow and enabled us to identify and fix defects quickly, minimizing project risk.

Furthermore, we worked out and applied the scheme of the job interaction order on Jenkins. Throughout the project, we conducted test refactoring and continuous analysis of automated tests, ensuring their relevance and reliability. To facilitate future testing, we also developed automated test templates.

In addition to our technical advances, we also focused on the organization and documentation of the entire project. We organized the testing process using TestLink. Moreover, we documented the testing process, creating various essential documents including checklists and test cases for manual testing, detailed instructions for deliveries (releases), precise requirements for test case design, a checklist to guide release delivery responsibilities, and a step-by-step system testing algorithm. These documents not only provided clear communication and coordination within the team, but also served as invaluable resources for maintaining quality and consistency throughout the project lifecycle.

Test Automation services

Technological Overview

Managed through a user-friendly interface system provides functionality at different stages of user’s work:

  1. Reference data management (RDM) systems allow user to manage and import data for various aspects of user’s operations, including: data about products, parts, materials; about technological routes, providing design and technological services, logistic services, etc. with automated workstations.
  2. Planning and management of production and supply:
  • Release management (long-term planning);
  • Modeling of complex distributed production and inter-factory cooperation;
  • Synchronized planning of development – production – supply – cooperation;
  • Provision logistic services, inter-factory cooperation in production and supply;
  • Operational planning and production management.
  1. Monitoring, KPI:
  • On-line monitoring of production/supply throughout the chain. In the context of the order/contract/supplier/cooperator/workshop/section.
  • From detailed (for a master) to consolidated (for a director), with the option of “drill-down” to details and operations.
  • Monitoring of the overall synchronization of work of plants/supply chain, visualization of economy and work efficiency in terms of synchronism and timeliness of plans implementation.
  1. The reporting function enables users to collect and upload various types of information in formats like XLSX, providing valuable information to specialists and management.
  2. Openness and usability of common external reporting and business intelligence tools.
  3. The system supports a role-based access control model that allows user to flexibly manage access to different functions and data levels.

The System is a web application which consists of two parts:

  1. HTTP server services implemented in REST style using Scala.
  2. Frontend implemented using Vue.js.

When working with the System end users do not need to install any additional software, since the SPM works in web browsers.

Users interact with data presented both in tabular form and in the form of interactive infographics (diagrams). During this interaction, CRUD operations can be performed, as a result of which requests are generated and are sent as HTTP requests to the Backend.

Further, on the Backend side the analysis of data correctness and saving to the database is performed. A response with data, in a universal for application format, returns to the Frontend, which is converted to display interface forms on the user’s side (in Frontend).

When working, different parts of the application can be physically in different places, because Frontend is lightweight and can work on almost any configuration. Backend, on the contrary, is very demanding on resources, because all the business functions are performed on it.

Validation check of the data is carried out both on the Frontend side: the correctness of entered data, verification of mathematical operations, etc., and on the Backend side: the correctness of received data, calculations of the values of the business function, etc.

When starting the system in a new environment, it is possible to primarily initialize data, as well as restore data integrity in case of errors.

In view of the foregoing, the SPM developers have very high demands on the performance of both mathematical algorithms and interfaces: the volumes of calculated structures in real projects reach tens of millions of units in each object (complex products produced by enterprises at different time horizons, taking into account all operations and movements, as well as optimization algorithms to ensure resolution of “conflicts” in competition for resources).

Testimonial

Svetlana Piterkina
Svetlana Piterkina
PhD, Consulting Director, LLC “Rightstep”

Together with JazzTeam engineers, we set up manual and automated testing processes in the project of developing of a new version of our information system for planning and monitoring of production and supply (SPM).

We started from scratch, largely based on experience and competence of JazzTeam crew.

During work, JazzTeam guys were readily immersing into the subject area, without understanding of which a high-quality solution of problems would be impossible, were sharing their knowledge and experience. Involvement in the project and interest in the result made it possible to build work with colleagues not as a “Customer – Contractor”, but as a united project team.

I would like to note the high professional level of the team as a whole, both in technical fields and in common culture of project work conducting and communication.

Result

In a short period of time, our team conducted an audit of the SPM system. We instilled a culture on the project where the testing process became a mandatory part of each sprint and the development process as a whole. We developed a comprehensive plan for implementing and automating testing procedures specifically tailored to the requirements of the project. By combining manual and automated testing, our team has thoroughly tested the system to ensure its stability and reliability. To improve testing efficiency, we designed and implemented a workflow for automated testing of new functionality and re-testing of fixed bugs. We created a series of documentation for the client’s team (manuals, release preparation instructions) to facilitate transparent communication and knowledge transfer.

Screenshots

Technologies

Databases: PostgreSQL.

Frontend: Vue.js, JavaScript, Mocha, Axios, Moment, Chai, Faker.js, log4js.

Backend: Java SE 8, Scala, Node.js, Selenium-Js.

Test Automation: Cucumber, Selenium WebDriver.

CI/CD and DevOps: Jenkins, Git.

Languages, Protocols, APIs, Network Tools: Java SE 8, Scala, Node.js, REST, Http.

Software Engineering and Management Tools: TestLink, Redmine, Confluence, IntelliJ IDEA.

Other Technologies: Chai, Faker.js, log4js.

Related projects

Recent Work

    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.