13. A system, the system comprising: a processor; a memory coupled to the processor, the memory comprising: a test script statement, comprising: an exposed method expressed in the test script statement; Application Programming Interface (API) calls characterized by API call types that navigate in sequence to the exposed method; logic, stored in the memory, that when executed by the processor, causes the processor to: determine a destination Graphical User Interface (GUI) object that exposes the exposed method; find an element path between sequential GUI objects in a GUI tree, where the element path leads to the destination GUI object, where the sequential GUI objects are characterized by GUI object types; determine whether the API call types in the element path between sequential GUI objects are compatible with the GUI object types in the sequence; obtaining, from a GUI object repository, validated action result for actions performed by the API calls on GUI object types in sequence; calculating API call type assignments for each API call according to the action results that specify valid API calls useable to perform actions on particular GUI object types; obtaining, from the GUI object repository, mappings of GUI object types, where each of the mappings comprise properties of a GUI object type; assigning GUI object types to each GUI object according to the API call types in sequence determined to be compatible with the GUI object types in sequence; determining a GUI object interactions count for the sequential GUI objects based on a configurable number of GUI object interactions for the sequential GUI objects; and generating a type inferencer message guide that explain how to transform data during data exchange between the GUI object.
13. A system, the system comprising: a processor; a memory coupled to the processor, the memory comprising: a test script statement, comprising: an exposed method expressed in the test script statement; Application Programming Interface (API) calls characterized by API call types that navigate in sequence to the exposed method; logic, stored in the memory, that when executed by the processor, causes the processor to: determine a destination Graphical User Interface (GUI) object that exposes the exposed method; find an element path between sequential GUI objects in a GUI tree, where the element path leads to the destination GUI object, where the sequential GUI objects are characterized by GUI object types; determine whether the API call types in the element path between sequential GUI objects are compatible with the GUI object types in the sequence; obtaining, from a GUI object repository, validated action result for actions performed by the API calls on GUI object types in sequence; calculating API call type assignments for each API call according to the action results that specify valid API calls useable to perform actions on particular GUI object types; obtaining, from the GUI object repository, mappings of GUI object types, where each of the mappings comprise properties of a GUI object type; assigning GUI object types to each GUI object according to the API call types in sequence determined to be compatible with the GUI object types in sequence; determining a GUI object interactions count for the sequential GUI objects based on a configurable number of GUI object interactions for the sequential GUI objects; and generating a type inferencer message guide that explain how to transform data during data exchange between the GUI object. 14. The system of claim 13 , where the logic further causes the processor to: find multiple GUI object interaction paths that identify API calls that perform actions on the sequential GUI objects; validate useable GUI object interaction paths from the multiple GUI object interaction paths that control the actions performed on the sequential GUI objects; and determine a number of GUI object interactions in each of the useable GUI object interaction paths.