Skip to main content

Testing EVA

As a software company, we are committed to providing a robust and reliable solution for our customers.

To ensure that our software meets the needs of our customers, we utilize a combination of automated testing and the expertise of our Quality Assurance (QA) team. Automated testing includes regular unit-testing of all APIs to ensure correct and swift responses to calls. Our QA team focuses on a wide range of regression scenarios, with a strong focus on daily retail operations. This regression is covered with every 4 weekly Drop of EVA features and Apps.

Examples of regression tests done by the EVA team include but are not limited to;

  • Daily store operations (day open/close, transactions, returns, (Adyen) payments)
  • In-store logistical processes (stock counts, receive, shipping, stock movements etc.)
  • General visual and functional integrity of Apps
  • Basically: all functionality we intregrate into the core of EVA

While we conduct thorough testing, it is important to note that not all customer-specific scenarios can be covered. For this reason, and to ensure in general that our solution continues to cover your business needs as EVA evolves, we expect retailers to dedicate in-house or 3rd party resources to the testing of new EVA Drops and features.

Examples of customer-specific scenarios include but are not limited to:

  • Integrations (import / exports) with your 3rd party systems (shipping carriers, ERP, payment/giftcard providers, etc.)
  • Financial bookings as a result of your Cookbook set-up
  • The output of your custom Stencils

In such cases, it is the responsibility of the customer to test the software in their own environment and report any issues to our support team. If new features are delivered, we encourage customers to provide feedback via the JIRA ticket within a week of delivery. We believe that by working together, we can achieve the best possible results.

TL;DR New Black tests all generic functionality

When a new Core drop or monthly Drop comes out, it contains a lot of changes and new functionality. Rest assured: everything in our Drops is considered a generic part of EVA and is thus tested.

This means we do not expect our customers to have to test anything based on a Core drop for example to prevent issues on Production.

Where to test

We advise your designated testers to make use of the Beyond versions.