The following additional changes have been made in the Testimony v2.21 release.

Testimony Functionality Enhancement that has been done
Auto-clicker for pop-ups During long and complex playbacks, popups on certain transaction codes would appear and block the playback. An example is the network graphic in transaction C202 (Change/Display master recipe). The bot now automatically closes these windows if it can so you do not need to constantly monitor and look for blocking popups.
External session not found issue The bot will now login automatically when a user session is not found thus removing this technical error altogether.
Batch job log evaluation method New methods of batch job log evaluation dependent upon customer requirements – see the details in the new general parameters section for parameter BATCH_EVALUATION.
New profile parameter check The key additional profile parameter we have added is to ensure that “multiple” logins are allowed for a user on the target system.
New Bot checks The playback check step to ensure the bots are all correctly setup now also perform the following additional checks:
  • Correct theme is set on the bot
  • SAP GUI history is turned off
  • Bot executable is “authorized” (SAP GUI configuration)
  • IE security setting is correct
  • Bot machine screen resolution is “sufficient”
Defect Management extensions Additional fields have been added to the defect management grid. The message (if any) can be immediately seen in the grid. With the change layout you can also add in the message class, number and type. The “Root cause analysis” flag is also available within the grid as well as being a new filter option.
Dynamic ID linkages exposed The user can now see the dynamic ID’s that are created and whether they are “producers” or “consumers”. These are also now available within the new version of the investigate screen.
Batch job spool linkages Testimony now captures the batch job spool output (lists) during both the recording and the playback. These are currently not compared but are visible within the linkage explorer and investigate screen.
Add bots on the fly during playback Since bots running out of memory can now pause the playback, it is now possible to add bots into the landscape and resume with them. You can start up bots while the queue is paused. Once started and connected to the central system, you will see them in the Active bots in the monitoring section. Click on them and connect them (mark as active). Then resume the playback.
Bot RFC sleep mode It had been seen on some playbacks that the bots would go into a “sleep” mode such that RFC calls to them were “queued” and would not be run until the bot executable was brought into focus. This is now resolved and you will see the bot (in the logs) sort this issue out on start-up.
Bot version information Within the supporting infrastructure, those bots that are “active” will now display their bot version in the grid display. Before you start the playback, you can ensure that the bots are all on the expected version.
Generation of bot configuration file From the supporting infrastructure, you can now generate the bot XML configuration file automatically. You will still need to enter the username and password that the bot needs to use to logon and register on the central system (either in the XML file or on bot startup).
Test plan filtering Within the menu path Configuration -> Test Plans, the list of test plans can now be filtered extensively. You can restrict the list of test plans by various filter options.
Supporting Infrastructure filtering Within the bot supporting infrastructure, various filter options are now available to restrict the list of bots displayed.
Copying bot setup Within the supporting infrastructure, if you are setting up many bots in preparation for a playback, you now have the option to “copy” an existing bot entry. You will still to specify the unique Bot ID as well as the machine name.
Most Frequent Object Sorting After a playback has completed, one of the best places to see the results of the playback is to go to the “Most Frequent Objects” grid within the Playback Overview. From here you can now sort by the “Success “ per object type and focus in on those objects that are not 100 successful.
Manual dependency configuration It is now possible to configure thta certain (low volume) transactions must be run prior to other transactions running. For example, this might be for month-end dialog transactions running prior to batch jobs or stock replenishment jobs running prior to stock level transactions running. Please liaise with Basis Technologies delivery and support when configuring this as it is not appropriate for high volume objects.
Dynamic ID and copying of queues Previously if you copied an execution queue, the dynamic ID generation on that queue would need to be run again. Now the process of copying the queue will also copy across the dynamic ID’s, thus you no longer need to run this again.
Dynamic ID performance The performance of the dynamic ID generation program has been significantly increased by a factor of at least 5 (i.e. 5 times faster). Performance issues were previously seen on large recordings and execution queues which should now be resolved.
Bot Logging Extended information on what the bot is doing at any one time is now output to the bot logs.
Launch Investigate Screen from Defect list From the defect management list display, the user can now launch directly into the investigate screen. If there is more than 1 associated script failure, the first is selected and this is the script that the investigate screen will display.
Defect list shows number of failures The number of associated failed scripts to the defect is now displayed in the defect management list.
Orphaned Logins When using sampling or exclusions, it is possible that a user logs in but then has all of their scripts excluded. Thus, we would log the user on and leave them logged in during the playback. These orphaned logins are now removed prior to the playback.
Manually trigger data transfer If there is an issue after the recording is deactivated, it is now possible to manually re-trigger the data transfer process.


Was this helpful?

Yes No
You indicated this topic was not helpful to you ...
Could you please leave a comment telling us why? Thank you!
Thanks for your feedback.

Post your comment on this topic.

Post Comment