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

Testimony Functionality Enhancement Description
Exclusion of RFC parameters Ability to exclude particular parameters from the comparison for a given RFC. This must be the entire parameter name, not a sub-component
External session not found issue Z includes rather than /BTI/AUT includes during enhancement activation
Inbound / Outbound RFC data size limits New parameter to restrict the amount of data that can go into SHM
SAP GUI for HTML support Full support for SAP GUI for HTML. Internally tested and at SAP
Utility to delete test plan data Used for internal purposes first. Can be used carefully in exceptions
Investigate container changes Various usability changes for viewing expected / actual outputs
Bot RFC playback anomalies Inbound RFC scale out testing. Data types not matching up
Coverage Analysis and filter sets Coverage analysis now takes filter sets into account
IDoc’s added in error If partner profiles deactivated on target, IDoc’s added in error now ok
Logon scripts when SHM filled When shared memory filled up, logon’s weren’t captured
Protect beta functionality via password Ensure beta functionality cannot be inadvertently activated by customers
Missing roles from build Two key roles were missing from the standard build program
Dynamic ID broken in block build Fix delivered to resolve issue where scripts were left unprocessed
S/4 HANA transaction testing Issues found during internal testing on S/4 HANA 1909 system HD4
Block building memory usage Memory consumption during block building was very high
Inbound RFC exception handling Additional handling of edge case exceptions during inbound RFC
Residual inbound RFC in SHM Failed RFC calls were remaining resident in SHM during recording
Flag to indicate if written to DB Business transactions have new flag indicating if it was written to DB
Unprocessed scripts for inb. RFC Large inbound RFC blocks containing circular dependencies resolved
Exclusions on the fly This had issues in 2.21 (and prior) so this was fixed
Open new session using /o This never worked and caused anomalies in the playback
Transaction variants supported This caused issues during the playback but is now resolved
Central / Source client issue When these were the same system, client was causing issues
SAP GUI session number on S/4 Critical issue identified in S/4 systems with kernel assigning session number
User preferences issues in playback User layout tables deleted during playback in certain t-codes
Batch job number in descriptor More accurate change docs assigned by using job number in selection


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