System Testing

Choose your preferred deployment method.

YUNIT developers know the importance of systems tests to enable CI/CD.

Fast release cycles are only possible when functional test requirements are well understood and implemented by highly educated and trained Consultants and Developers.

The usage of Gherkin syntax is the preferred method of writing automated integration tests, and easy to understand for business and process owners. When tests fail during the release cycle the business stakeholders are able to understand which areas are affected and evaluate the criticality of the failure.

Example:

Scenario Outline: Add Product to Cart

Checks that cart is properly recalculated when items are added

Given I´m accessing the country site '<country>'

And I login with user '<email_address>' and '<password>'

And I select account with number '<account_number>'

When I add '<quantity>' items of '<product>' to cart

Then Product '<product>' with quantity '<quantity>' is in cart item '<position>'

Then Cart Item '<position>' has a total price of '<total_price>'

Automated tests serve in particular powerful to prevent having business users re-test the same functionality over and over with every minor feature release or hotfix. In conjunction with a CI/CD architecture having systems tests verify the core processes is a mandatory prerequisite to meet.

"We have tests!"

YUNIT Consultants often observe in large or medium-sized implementation projects that existing test cases are written in a way which misses the intended purpose and doesn´t effectively test the scenario. If in your project the rate of false positives or negatives being reported is high this problem affects you.

To ensure that tests are reliable in SAP integrated projects it´s important to have consultants and developers in the project team with not only Hybris experience but a strong SAP SD background in addition.