All related posts: Reference Page – GP/QTP Automation VBScript limitation Since VBscript supports only Variant type attempts to use variable in a COM call with an argument defined as “[in, out] BSTR * “ reasonably end with “Type mismatch” error. This error is generated by the COM object itself rather then VBscript interpreter since the object gets string [...] ...
All related posts: Reference Page – GP/QTP Automation General concept The Application object provides only a few methods for simulation of GUI interaction required in Test Automation. However, ExecuteSanScript method allows overcoming of that limitation. The piece of sanScript code pre-written or dynamically generated could be passed-in to Microsoft Dynamics GP runtime engine, and compiled and executed [...] ...
All related posts: Reference Page – GP/QTP Automation Documentation Microsoft Dynamics Great Plains Continuum API Guide (http://mbs.microsoft.com/downloads/public/GP90Docs/ContinuumAPIGuide.pdf) is the only main published document, which is pretty short though. Many of available functionalities are just mentioned or briefly referenced but not documented in details. Exploring DLL library directly I was able to retrieve more details on ...
All related posts: Reference Page – GP/QTP Automation Purpose: extract object descriptions from Dexterity Dictionary and create custom XML-based GUI Map file for QTP. Used resources: Service Functions – XML (QTP, VBScript) Option Explicit ' Purpose: Map GP Dexterity GUI into XML file ' Requirements: GP App started (don't have to login) 'Output: ".....\DexGUI.xml" Dim GPApp, objForm, objWindow, [...] ...
All related posts: Reference Page – GP/QTP Automation Dexterity Objects Hierarchy Internally, Dexterity objects have the following hierarchy: Application Forms Windows Window Fields (input boxes, check/radio buttons, buttons, etc.) The hierarchy is stored in the Dictionary file. Visually, Dexterity objects are presented as: Panels Dialogs GUI Controls (input boxes, check/radio buttons, buttons, etc.) In order to use [...] ...
All related posts: Reference Page – GP/QTP Automation Overview: COM and Automation COM, Component Object Model, is Microsoft framework for developing and supporting program component objects. Whereas Microsoft’s Object Linking and Embedding (OLE) provides services for the compound document that users see on their display, COM provides the underlying services of interface negotiation, life cycle management (determining [...] ...
Dot NET GUI System.Windows.Forms standard GUI objects Successfully recognized and mapped by QTP Online reference: http://msdn.microsoft.com/en-us/library/system.windows.forms.aspx System.Windows.Forms custom GUI objects Successfully recognized by QTP but mapped as generic object class “swfObject”. Hence the limitations operating it. However, each object and its custom methods could be inspected manually (with Object Spy) and ...
All related posts: Reference Page – GP/QTP Automation 1) Automation Requirements Summary Automated Testing solution should be open, scalable, robust, and friendly for the continuous maintenance Test Data model should be open, scalable, and extendable. All the settings must be customizable without code changes. Test Case scripts dependency on a specific spreadsheet or file structure should ...
