Natural Screen Tester provides a number of different tools that can help to log, trace and analyze performance and functionality.
The Server Log includes information as to the Server's activities and problems. The contents of the server log file are defined according to the settings configured in the Server Parameter>Log node. The Server Log can be accessed from Natural Screen Tester Designer or via an external browser. Administrators who do not have Natural Screen Tester Designer will access the Server Log from the Designer. Administrators who do not have Natural Screen Tester Designer will access the Server Log via an external browser.
There are several possible levels and each level includes the levels above it. For example, the Debug level also logs Normal, Warnings and Errors Only levels. See also Configuring the Server: Log | Viewing the Server Log in the Getting Started documentation.
A log used for fine-tuning connection pool parameters or identifying problems of the different connection pools is written within the server log. The server log should be set to no less that the Info log level, in order to see connection pool logs. Once the project is in the production phase, Error level is the recommended level to use. It is possible to set a different detail of logging for each connection pool: None, Errors, Warnings, Information and Details.
See also Connection Pools: General Parameters.
As part of the procedure work flow definitions, it is possible to define that at some point in the procedure a message will be sent to the log. This is implemented using the Log Message Node (Refer to Working with Procedure Nodes and to General Nodes (Relevant for both Flow and Test Case Procedures), Test Case Procedure Nodes and Flow Procedure Nodes.
Natural Screen Tester enables generating a log that includes debug data regarding procedures that fail in runtime. The log includes a snapshot in ASCII characters of the screen that caused the failure.
To log data regarding procedures that fail in runtime
In the <nsr_home>/config/log/gxlog_config.xml file under the com.sabratec.util.flow.error_tracking category tag, change the <level value="off"/> line to be commented and uncomment the <!-level value="debug"/--> line.
Restart the Natural Screen Tester Server.
The log will be created in the <nsr_home>/log directory, and the file names will have the following format: debugging_error_in_%I_%t.log, %I being identifying information about the user and procedure name, and %t being the timestamp. The location and name of the file can be changed in the gxlog_config.xml file.
The GCT Trace File log enables recording a file, which traces the connection communication (connection pool or user) between the Natural Screen Tester server and the host, for each connection. It is possible to define whether a single trace file will be created, replacing the previously saved file or whether the data will be saved to a new file on every new connection or session. Identifying the separately saved files is possible by inserting identifying parameters in the file name (the session ID, creation time and/or connection ID). It is highly recommended to create a separate file for each session/connection or creation time. Note that trace files can be created from within the session definition overriding the application definition. This is recommended as it does not conflict with other existing sessions.
Refer to Recording Trace Files in the Designing and Developing a Test Case documentation for details regarding recording trace files.
Refer to the Session View in the Designing and Developing a Test Case documentation for details regarding overriding properties per session and also for details on navigating within a session in replay mode.