Q:We're using QTP v8.0 and capturing GUI with formatted numeric fields such as currency, etc.

with commas
and decimal. QTP does not capture the input (so that I can parameterize this later), but captures the formatted
field after entry. How do I make QTP capture my input instead of the formatted field? How do I validate this
formatted field that it contains valid input?
A:1. If your numeric fields are edit boxes and QTP record commands like WinEdit.Set "1,234.56" Then just
replace Set command with Type command like WinEdit.Type "1234.56"
2. In order to check the numeric value of the formatted field use VBS functions to convert from strings to
numbers.
For example:
text = WinEdit.GetROProperty("text") ' returns string "1,234.56"
num = CDbl(text) ' returns number 1234.56
num1 = CInt(text) ' returns integer number 1235
Q:In using the Mercury Diagnostics 3.0 what additional information can I retrieve during my testing and
performance evaluation?
A:Diagnostics 3.0 offers 360-degree monitoring from end-user, application, and system perspectives.
Allowing customers to detect problems in the application as well as in all connected systems and
environments. Within the application itself, you can get detailed visibility at the component, method, SQL
statement and even line of code levels.
Q:For Diagnostics 3.0, what is the probability of diagnosing all the way down in the People Soft Applications?
A:Diagnostic 3.0 supports most common ERP/CRM packaged applications from the end user and system
perspectives. Within the application level, full support for detailed data capture of PeopleSoft application is not
yet available. We work with PeopleSoft closely to extract performance information from the standard
PeopleSoft APIs to supplement our own capabilities for monitoring and diagnostics of PeopleSoft applications.
Q:I am trying to run tests from command line using QTPlaunch.exe with close option after executing the test.
In my driver script execution it will set results file folder and other settings. Once the test is scheduled at the
end it will ask for save option, this causes manual interference to accept yes or no. We need to fix this in order
to execute the test unattended fashion using QTP command line utilities
A:We suggest you try restoring the default settings at the end of the test run to alleviate the problem. Note
that in general, we recommend that using the command line option for automation be dropped in favor of
using the QTP Automation API. If these suggestions do not resolve your issues, please do not hesitate to
contact CSO for further assistance.
Q:WinRunner. The data table has excel-like functionality but is not completely excel-like. For example you
can't copy/paste like in excel. When will it have the same excel-like functionality?
A:Unfortunately, there are no plans to add this functionality.
Q: VB Script code opens a command window, changes to the path C:\ and executes DIR command
Dim oShell
Set oShell = WScript.CreateObject ("WSCript.shell")
oShell.run "cmd /K CD C:\ & Dir"
Set oShell = Nothing
For more Information
http://www.mercuryevents.net/wwuserconf2004/index.cfm?action=ask_rd
-> to goto command prompt
SystemUtil.Run "cmd"