QA Consulting and Change Management for Enterprise Resource Management Product

  • 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: Project Management, Collaboration and Bug Tracking; IntelliJ IDEA; Git; CI/CD Automation Servers; Jenkins; Apache Log4j; TestLink; REST; WebDriverJS; Data Bases; Node.JS; Test Management Tools; Selenium WebDriver; MindManager; Java; Frontend; JVM Languages; IDE; Scala; Backend; Vue.js; Redmine; Testing Frameworks; JavaScript; JavaScript Frameworks; NetCat; Various Editors; Selenium-Js; Mocha; Cucumber; PostgreSQL; JavaScript Libraries; Source Code Management (SCM); Standards and Protocols; Test Automation; faker.js; Test Automation; CI/CD and DevOps; Chai; Axios; Languages, Protocols, APIs, Network Tools; Network Tools; Software Engineering and Management Tools; Confluence; HTTP/HTTPS; Java Libraries; Logging Libraries; Moment.js
  • Team size (3):
  • 1 Project Manager
  • 2 QA Automation

Project summary

thumbnail-image The SPM (“Lean SCMo ERP”) of the company Rightstep (hereinafter the Customer) is intended to manage production and logistics chains (internal and external) of industrial enterprises.

The SPM (System of Planning and Monitoring, hereinafter the System) supports both Western and Eastern industrial models, including distributed productions 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), updated “Novocherkassk Rodov’s system” (improved planning through the “proportionality file”, 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.

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).

The enterprise resource management system (the ERM, hereinafter the system) is intended for planning, managing, monitoring and analyzing of the operation of any enterprise using an information system. When working with the system, the end user does not need to install any additional software, since the ERM works directly in the browser.

Briefly about the system functionality

  1. Reference data management (RDM). The system allows you to manage or import 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. Reporting. It supports collection of various information and uploading in XLSX files format (and other formats), in an informative for specialists and managers, in various aspects.
  2. Openness and usability of common external reporting and business intelligence tools.
  3. Support of role-based access control model. The system allows you to flexibly control the level of users access to various functions and data.

Customer: “Rightstep” company

Rightstep is a consulting and IT company that focuses exclusively on solving problems in planning and managing production and supply.

Rightstep is a team of successful professionals. The main experts and specialists of the company are together since 2003, with extensive production and IT experience in staging and commissioning of control systems at dozens of industrial enterprises.

The goal of Righstep company is to make every manufacturing business as efficient as possible. To ensure, first of all, rapid execution of customers’ orders (including state orders), moreover, “just in time”, “exactly in quantity”, with minimal production costs and high productivity.

Briefly about architecture

From the point of view of implementation, 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 configurations. 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 new environment, it is possible to primarily initialize data, as well as restore data integrity in case of errors.


Stack: Java SE 8, Scala, Node.js, JavaScript.

Frameworks: Vue.js.

Infrastructure: Jenkins, Git, TestLink, Redmine, Confluence, IntelliJ IDEA.

DB: PostgreSQL.

Test libraries: Mocha, Cucumber.

Other libraries: Selenium WebDriver, Selenium-Js, Axios, Moment, Chai, Faker.js, log4js.

Protocols: REST, Http.


Project features

  • Before our appearance on the project, the customer had no set up system testing process.
  • The customer expected us to actively participate in organizing setting of testing processes, formalizing processes, proposals and introducing a testing culture, as well as sharing the best practices of our extensive automation experience.
  • The work was clearly phased, each stage was planned and agreed with the customer and was limited by deadline.

Project result

  • For a short period of time, we conducted an audit of the SPM system with subsequent evaluation and implementation of manual testing, transfer to test automation.
  • A plan for implementation and automation of testing of the system on the project has been developed.
  • Manual and automated testing of the system was conducted.
  • 158 autotests were implemented.
  • A number of instructions for customer’s teams (manuals, instructions for preparing for releases) have been developed.
  • The workflow for automated testing of new functionality and re-testing of fixed bugs was developed and implemented.
Test automation

The company’s achievements on the project

  • Successful experience in developing a detailed plan for automated testing of the system with its subsequent implementation on the project.
  • Implementation of CI at the customer’s side.

What we did on the project, our responsibilities:

  1. We wrote and implemented a plan for implementation of testing and its automation, organized and carried out manual and automated testing of the SPM system.
  2. We wrote a basic (60 tests) and a complete test sets (158) for smoke and regression testing.
  3. We installed and launched Jenkins and TestLink servers, installed and configured the plugin for integrating results from Jenkins into TestLink. Also, in the process of work, the source code of the plugin was customized to our needs.
  4. We worked out and applied the scheme of the job interaction order on Jenkins.
  5. Autotest templates were created for subsequent reuse.
  6. We organized testing using TestLink.
  7. We performed refactoring of tests, on an ongoing basis conducted an analysis of autotests with their subsequent updating.
  8. We performed documentation of the testing process, created a number of documents:
  • checklists and test cases for manual testing,
  • instruction of deliveries (releases),
  • requirements for the design of test cases,
  • checklist to assist somebody who is responsible for delivery of release,
  • step-by-step system testing algorithm.

Customers’ testimonials

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.

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.