Setting up a test environment

Preliminary

A test environment should ideally be located on a (sub)-network with a network manager of his own. If you create a standalone test environment and install all components on one machine, you do not need a copy protection key for network manager but are limited in testing real network issues.
You should familiarize yourself with SDK Tools and their possibilities. Please read the detailed documentation!

Test environment for test equipment developers

A recommended setup is build with at least two machines (physical or virtual). The primary tool is OrderSim to create orders.

  • Machine A: Network Manager , SDK Tools (and possibly a DMS)
  • Machine B: SDK Tools and your test equipment

If you have 3 or more machines, use this setup:

  • Machine A: Network Manager, SDK Tools
  • Machine B: SDK Tools (and possibly a DMS)
  • Machine C: SDK Tools and your test equipment
  • Machine D: SDK Tools and your test equipment
Test environment for dealer-management-system developers

A recommended setup is build with at least two machines (physical or virtual). The primary tool is TestClient to simulate workshop test equipment.

  • Machine A: Network Manager , SDK Tools and your DMS
  • Machine B: SDK Tools

If you have 3 or more machines, use this setup:

  • Machine A: Network Manager, SDK Tools
  • Machine B: SDK Tools and your DMS
  • Machine C: SDK Tools and your DMS
  • Machine D: SDK Tools and your DMS (if you have multiple interfaces into asanetwork)