Test Data Automation's System Requirements for Windows Installation
    • Dark
      Light

    Test Data Automation's System Requirements for Windows Installation

    • Dark
      Light

    Article summary

    Please ensure that all pre-requisites are complete prior to installation.

    1.1 System Requirements Met

    • Windows Server 2013 Enterprise / 10 Pro Minimum - 64-bit Edition

    • 64bit Processor (i5 minimum – Intel Core i7 recommended)

    • Minimum 16GB Ram (32GB Recommended)

    • Minimum 80GB Hard Drive space

    • If using Database Generation functionality, these additional requiremets apply:

      • Port 8091 (configurable) open for inbound communication (both on the network level and on the Windows Firewall)

      • A fully-qualified domain name (FQDN) for the Windows Server machine to be accessed from browsers on the user machines

      • (Optional) If the TestModeller instance uses HTTPS, an SSL certificate for the Windows Server machine as well. If one is not provided, a self-signed certificate will be automatically used instead, resulting in users having to accept using it in the browser.

    • (Optional) Ports 8081-8085 open for inbound communication (both on the network level and on the Windows Firewall). Only if utilising additional VIP servers

    • (Optional) Ports for outbound communication (both on the network level and on the Windows Firewall) to any external application that VIP needs to connect to (e.g. Databases). This depends on the use case.

    Please Note: ARM Chip architecture is not supported.


    1.2 Software Requirements Met

    Windows Server Machine:

    • .Net Framework 4.8

      • If using Database Generation functionality, the Developer Pack must be used.

      • Otherwise, the Runtime is enough.

    • Java 8

    User Machine:

    • Internet Browser (Google Chrome recommended)


    1.3 Copy File to Windows Machine

    VIP installation file downloaded from link provided by Curiosity.


    Common Blockers

    We commonly see the below issues during installation. 

    By completing the checklist above, these blockers will be avoided:

    • Environment not provisioned

    • Insufficient space

    • Ports not open

    • Installation files not downloaded prior to the meeting