If this message is not correctly displayed, click here


Newtest version 3.1

Dear Newtest customers and users,

We are pleased to inform you that version 3.1 of the server is available at this time. This version brings you the following new features:

All robot and NTBR flows are encrypted, either via STCPIP or by the new NHTTPS using TLS available on version 8 robots.

The benefit of using TLS is that it is based on a public protocol which has already been subjected to numerous attempts to break the encryption. Use of TLS therefore constitutes good practice from a security point of view.TLS flows can be activated in 2 ways:

  • NTBR (v8) and web users to IIS: known port 443
  • Robots (v8): NHTTPS flows to a dedicated listener (NMC port configurable to needs)

Using TLS involves a twofold installation of certificates on NMC/NRS:

  • on IIS to access the NMC/NOP/NRS web interface
  • on a new NHTTPS listener, using its own certificate (signed by ip-label)

Newtest 3.1 documentation describes in detail how to activate SSL for both of these.

Robots located behind a collector are encrypted with the TCPG (STCPIP) protocol for Robot 8 and the Newtest Gateway(release scheduled for October)

This diagram summarizes the flows supported in version 3.1:


Please note these important requirements:

  • Starting with version 3.1, the product no longer supports historical standard HTTP (bidirectional). This means that prior to upgrading to version 3.1, migration to STCPIP should be carried out for any 7.6 version robots which require it.

  • Robots behind a collector must necessarily be upgraded to version 8 for migration to the server 3.1 so that they can support the TCPG protocol to the Newtest Gateway (NGW). This operation must be performed by a certified Newtest consultant.

NAM (the optional Newtest Alerting Module) offers correlation of alerts between robots and scenarios. It also deals with “suspended” or “out of range” statuses.

Below is a list of alarms tracking when they occurred over time. Additionally, details of each alarm are broken down by condition for each robot:


For example, an alert is issued only if 100% of the robots return an error on a given application. This percentage may be adjusted to be made more or less resistant to false positives.

Single sign on: LDAPS (security option to activate) is supported, in addition to a function for synchronization on request for users added to your directory (AD).

We are here to help if you need further information.


ip-label Marketing team.

ip-label ip-label twitter iplabel google linkedin

If you do not wish to receive our mails, then click here.