(v1) Internal Organization
- Marcin Galczynski
Analytics
Internal organization
This documents describes the internal organization of the product and the basic components building up the features and functions of the product.
Environments
At the core of the test creation and execution, we need information on the system landscape and connectivity details. This information builds the logical structure of the IT landscape with the existing systems under test through configured connections.
Depending on the specific system the environment definition will point to one or more technical endpoints which name a specific system, URL path (as applicable) and relevant logon credentials.
Below example shows how Environments map to specific systems and services.
Please note that this example is limited in content for simplicity. In a typical scenario there are multiple services across multiple tenants, and dozens of environments for testing and useful as data sources.
A successful setup will include connection to productive and non-productive systems. Connection to test and development boxes enable test execution and shift-left testing approach. Connection to production systems is needed for easy capture of test data
Test configuration
Int4 Suite Cloud Edition is built around the concept of Test Configuration. It contains configuration for each test execution step and define the interface under test, test conditions, and necessary data manipulation employing a Variable concept. Read more about them in the dedicated section of this manual: Reference for test configuration objects
Test cases
A test case is a basic entry representing data for single test execution. The test case execution happens in the context of the assigned Test Configuration in a specific Environment.
Test creators can link test cases into scenarios. It enables testing of complex, multiple-step flows, for example, the Order-To-Cash process.