Posted by Albert Gareev on Mar 04, 2010
All related posts: Reference Page – GP/QTP Automation Question The question was asked here. I need to make a small change in xml file created without re-mapping a window. How can I manually get Dexterity GUI field names from GP? Answer You can do that by accessing “Tools\Resource Descriptions\Windows” item of main menu of any Dexterity Window. […] ...
Posted by Albert Gareev on Dec 28, 2009
GP/QTP Automation: Conclusion but not closure The main question – whether it’s possible to automate Microsoft Dynamics Great Plains application testing (OS Patch smoke tests, UAT/Regression tests) – was answered positively, and proven in the actual implementation of automated test scenarios. Tools and Technologies Standard GUI recognition method (via Windows Handle) used by UI Automation tools […] ...
Posted by Albert Gareev on Dec 23, 2009
All related posts: Reference Page – GP/QTP Automation Dexterity Macro Limitation and Suggested Workaround One of the major limitations identified in Dexterity Macro System is totally hard-coded data with no functionalities to read them from any external source. To overcome this issue we can dynamically generate Dexterity macro text file from a pre-built XML template. After the file […] ...
Posted by Albert Gareev on Dec 21, 2009
All related posts: Reference Page – GP/QTP Automation Answer According to the documentation, there are no loop operators defined in Microsoft Dynamics Great Plains Dexterity Macros. However, the macro language provides other commands to workaround the issues in the most required cases. Workarounds 1. Capture values of GUI fields (in a loop) Use DumpFieldBegin…DumpFieldEnd commands. 2. Window synchronization […] ...
Posted by Albert Gareev on Dec 07, 2009
All related posts: Reference Page – GP/QTP Automation Dexterity Macro Limitation One of the major limitations identified in Dexterity Macro System is totally hard-coded data with no functionalities to read them from any external source. Running scripts that always look for exactly the same account number or check balance on always the same date would provide a little […] ...
Posted by Albert Gareev on Nov 12, 2009
All related posts: Reference Page – GP/QTP Automation Documentation Microsoft Dynamics Great Plains Dexterity Programmer’s Guide: http://mbs.microsoft.com/downloads/public/GP90Docs/Prgv2.pdf Refer to “Part 7: Software Engineering, Chapter 34: “Testing Your Application”. Microsoft Dynamics Great Plains DexterityMacro System in “Recording Test Cases” document: ...
Posted by Albert Gareev on Nov 09, 2009
All related posts: Reference Page – GP/QTP Automation The problem Those who tried sanScript code examples on their windows/objects probably noticed that Great Plains refuses to execute some instructions referring to certain objects even if they were successfully mapped with Dexterity GUI Mapping Script or with GUI Capture Script. And while highlighting window controls you may see that some […] ...
Posted by Albert Gareev on Oct 26, 2009
SanScript, Visual Basic, and VBScript functions implementing the “Highlight in Application” feature as in QTP Object Repository Manager. All related posts: Reference Page – GP/QTP Automation VBA/SanScript function – put in your Excel VBA macro file Note. Ignores sanScript errors VBScript function – put as Dexterity Interface Class method Note. If you use it as an embedded function don’t […] ...
Posted by Albert Gareev on Oct 12, 2009
A script capturing Dexterity objects (both GUI and non-GUI) contained within the window. Great Plains application is required to be up with the particular window invoked and activated. All related posts: Reference Page – GP/QTP Automation Programming language and tool: VBScript / QTP. The script produces an output as XML file with the structure similar to QTP object […] ...
Posted by Albert Gareev on Sep 25, 2009
All related posts: Reference Page – GP/QTP Automation The following object implements interface from QTP side. Function Libary Source Code Used resources: Service Functions – String (QTP, VBScript) Declare and initialize: ...
Posted by Albert Gareev on Sep 23, 2009
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 […] ...
Posted by Albert Gareev on Sep 21, 2009
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 […] ...
Posted by Albert Gareev on Sep 10, 2009
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 ...
Posted by Albert Gareev on Sep 09, 2009
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) ...
Posted by Albert Gareev on Sep 07, 2009
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 […] ...
Posted by Albert Gareev on Sep 01, 2009
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 […] ...
Posted by Albert Gareev on Aug 26, 2009
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 ...
Posted by Albert Gareev on Aug 24, 2009
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 ...