(v1) Testing scenarios and flows
- Marcin Galczynski
Analytics
Int4 APITester allows for execution of single test cases and also testing scenarios with varying complexity, consisting of multiple test cases. Test cases to be executed as scenario should be contained in single folder in APITester.
Testing scenarios requires good understanding of the product basic concepts. Please familiarize Yourself with the relevant sections of the manual and basic examples before proceeding.
Simple testing scenario - mass regression execution
In simple scenarios, multiple test cases are executed in series, based on single Automation Object.
In such a scenario, selecting a folder and running all test cases (using Execute All button) will produce a test report with execution details and pass/fail information for each test case. There are no dependencies between the test cases, and each one will be triggered.
To create such a scenario You need to create an Automation Object and create test cases, either using Message Selector or Robotic Crawler.
These simple scenarios are good for mass testing of messages, usually to execute regression testing or to generate data in the test system.
Complex testing scenario - linking test cases to enable business process flow testing
Int4 Suite allows for complex scenarios, with test cases linked, passing data from one test case to another, resulting in ability to test multiple step business processes. Such a test usually requires mixing different testing types (Inbound, Outbound and UI test cases) and requires multiple Automation Objects to run.
This scenario contains six test cases representing test for a sales order business flow.
This example is based on a popular Sales Order process, with delivery and invoicing. This is a well recognized process that is easy to relate to. Int4 APITester is data, format and process agnostic and can be configured to support any ECC or S/4HANA integrated scenario.
Configuration for complex scenarios
To enable complex scenario execution we’re looking first at making sure all the validation and transactional steps are configured. In the above example, validation and execution is being realized thru API calls. In other words, by calling the API that retrieves or commits a business transaction.
Linking test cases
In order to ensure seamless data flow between the test cases, certain configuration for Test Configurations and linkage between the test cases (Parent Test Case setting) need to be properly set up.
Description of such configuration is heavily dependent on the actual API’s and the scenario. Please see our Archived Example Scenarios Navmarchived for some ready-made examples.
Please note, that execution of this test scenario will create documents in the respective systems and process them accordingly. Automation Objects with Variables are used to point Int4 to specific interfaces and data elements in the messages, to ensure that the executed transactional steps are only relevant to the business documents in the specific scenario test execution.