Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Here are links to recorded demos for our teams and customers. You can find the power point presentations used for these demos in the downloads section here:

For Configuration Engineers

Schneider Electric demo

Live demo for client
Table of Contents
minLevel1
maxLevel6
outlinefalse
stylenone
typelist
printablefalse

Automation testing

Pricefx offers comprehensive end-to-end automated front-end tests for PriceFx‘s solutions. Through this we can reduce the time spent on regression testing and increase the quality of our application by eliminating manual tasks and increasing the user confidence in our solution.

When it comes to automated testing we like a testing approach with easy to understand automated tests for non-technical people

Tools

One of the tools we use in Pricefx for testing is Cypress. Cypress is a JavaScript-based end-to-end testing framework allowing you to easily write and maintain tests. It can be implemented into PriceFx gitLab CI/CD jobs. Moreover, it has the ability to write tests that everyone can understand.

Example of the testing process

Identify use case, create test case, define data and execute manually 

Test example


 Verify defined attributes of validated product.
Preconditions:  
Check PX table and fill expected cost values for tested products  
Recalculate LPG before test  

//1) Open targeted LPG 
//2) Find attributes: (MinimumMargin, Margin, MinimumMarginPrice, FinalPrice, Cost)
//3) Verify attributes for expected values 

Duration of one manual execution: 3 - 5 minutes

Create automation test in Cypress 

  • Create required test in Cypress using QA‘s PC

  • Reusable tests (run over and over again)

  • Data management for test

  • Create test in readable form for non-technical people with using PriceFx‘s library of commands

Duration of creating mentioned test: 1 - 2 hour
Duration of running: 1 minute

Testing using a library of commands

Upload tests to git repository

  • Can be run every time when needed

  • After deployment

  • After change in code

  • On request

Automatically generated outputs

  • Video from every test

  • Screenshots with errors

  • Report

Report example

A report will usually include the tests, results, and testing time. Below is a sample report showing the results of the test(s), including a recorded video of the tests running on the servers.

FEMargin-library.spec.js.mp4

Pros (plus)

  • E2E tests

  • Reduced time in regression testing

  • Elimination of manual tasks 

  • Increased user confidence with the solution

  • Ease of use for non-technical people

Cons (minus)

  • Only on UNITY

  • Front end tests could be a little fragile

  • Maintenance of the tests

  • QA person is still needed on the project

Info

Easy way how to install and run cypressCypress. Write a the first test and set it up on any partition. Learn more here.