What issues have been fixed in SilkPerformer V 5.1?
The following issues have been fixed in Silk Performer V 5.1
Issue: Long error messages in TrueLog Explorer"s info view are cut
For verification functions, TrueLog Explorer"s info view contains an "Info" section, which
shows the success or failure of the given verification function. If the text verified by
the given function is rather long, and the verification fails, the error reason is not
visible because the string is cut at some point.
Issue: A memory leak occurs when the rendered HTML view contains a text selection.
Issue:When trying to insert verification or parsing functions in HTML pages consisting of frames, you may get a message that the selected text is not part of the visible page content, and that the verification/parsing function can therefore not be inserted. This behavior may occur when a frameset document is only partially updated (i.e.: some, but not all frames of a frameset have been replaced by other HTML documents).
Resolution: Fixed. Issue: If you select "apply filter" (Settings / Options) in the options dialog, the filter is only applied in the upper tree-view, not in the lower tree-view. This applies only when the TrueLog Explorer is in compare mode.
Issue: A problem displaying URLs can occur in TrueLog files in the TrueLog Explorer.
It may happen that every URL within a HTML page rendered in the TrueLog Explorer is displayed differently than the same URL in the original HTML page.
Issue:Open a Replay TrueLog and load the corresponding Record TrueLog by choosing "Analyse Test / Compare your test run". If you press the "Find Next" button in the "Step through TrueLog" dialog while the record TrueLog is still loading, the tree selection is moved to the next node of an API call in the upper tree view, but not in the lower tree view.
Issue: Visual content verification does not work on encoded (e.g. gziped) content, because the desired text cannot be found in the corresponding HTML source code.
Issue:Removing a script from a project while running an All Day simulation causes the Silk Performer Workbench to stop responding. This may also occur if you open the All Day Progress Monitoring dialog after removing a script. (6527)
Issue: A user type cannot be found although it is defined. This problem may occur if a project contains at least one script (.bdf file) that is located in the project directory and another is located somewhere else.
Issue:"Customize Session Handling..." may modify the data to post to the server of a WebUrlPostBin or WebPagePost function call in a defective way.
WebUrlPostBin and WebPagePost specify the data to transmit to the server not in the form section, but within the function call.
If that data block is getting rather big (> 10000 bytes) and contains session information, Customize Session Handling modifies the mentioned function in that way that either the script cannot be compiled or the parts of the data are simply cut off.
Issue: The Reorder does not generate function calls when the connection gets closed and the server does not return a response.
Issue: "Customize Session handling
" may miss to properly escape a backslash if the value of the variable exceeds one line.
Issue: IDL compiler reports errors on:
- valuetype factory methods raising errors
- String value assignment to a const WStringValue(Box)
const ::CORBA::WStringValue wsv = "string constant";
factory create() raises (exception); // not CORBA compliant
Issue: A revisiting user with TrueLog on Error enabled, using "Store TrueLog: Based on content history" setting, doing a WebPageBack function call may cause a PerfRun crash.
Issue: PerfRun may crash after a test.