DOT-Verifier, a non-regression testing (NRT) tool 2017-07-21T11:40:39+00:00

Application Servers

Compatible avec JBoss

Compatible avec WebSphere

Compatible avec WebLogic Server

Compatible avec Apache Tomcat

Collaborative Platforms

Compatible avec IBM RTC

Compatible avec Visual Studio

Compatible avec JIRA

SCM/Integration

Compatible avec git

Compatible avec SUBVERSION

Compatible avec CVS

Compatible avec artifactory

Compatible avec Visual Studio

Compatible avec IBM RTC

Compatible avec Arcad

Compatible avec SYSchange

Provisioning

Compatible avec docker

Operating Systems

Compatible avec z/OS

Compatible avec UNIX

Compatible avec Windows

Compatible avec Linux

Functional and technical architecture

DOT Verifier architecture

It’s easy for end-users to record test scenarios directly from the interface they usually use. The DOT-Verifier tool automatically records:

  • all user actions performed in the interface (keystrokes, mouse movements),
  • all screens called,
  • all data used in the database(s) (1) or in external files,
  • all reports generated (PDF or plain text).

Validation allows for:

  • the exclusion of certain screens’ fields that should be systematically excluded from the comparison (date/time, user, etc.),

  • the exclusion of certain fields from the database (such as time stamped fields).

Note that it is possible to return to a database’s original state after recording a scenario, and that each scenario is independent from the others. Because of this, they can be replayed in any order.

For each new application version there is a corresponding replay that contains the related scenarios which will automatically be made available for this new version. PDF reports are generated once the replay has been performed.

  • Modifications to data, recordings and fields
  • Modifications to data structure: (field addition/deletion, size)
  • Modifications made in the user interface
  • Modifications to PDF or text reports

For most test scenario tools, it is very difficult to update an existing scenario after modifications in the programs. Often, it requires complete re-entry of the scenario or script modification.

DOT-Verifier functionalities will help you to facilitate this task:

  • A system of stopping points makes it possible to execute an already-recorded scenario and then take back control over execution of a selected step.
  • All of the values entered on a screen can be modified. Of course, it is also possible to add new entries, for example when a new field has been inserted into a screen.

  • DOT-Verifier can be integrated into Jenkins via plugins. In the framework of setting up continuous testing processes, Jenkins can steer performance of DOT-Verifier scenarios and the delivery of comparison reports.
  • DOT-Verifier can also be integrated into most non-regression testing (NRT) tools on the market, in which case it supplements the reinitialization and comparison part of test data.
Watch a demo

DOT-Verifier

Brochure

Find out more about DOT-Verifier by downloading the brochure!

Download the Brochure

Customers


Help & Support
Helpdesk .........................................
Contact us .........................................
Book a demo