Recognizing Industry-Standard Controls

Before TestComplete can validate an object using a checkpoint, TestComplete has to recognize the object first. If your tested applications use out-of-the-box, industry-standard controls, you’re in luck. For example, TestComplete knows all about JavaFX TableView, Infragistics UltraGrid and Microsoft DataGridView controls by default. If you create a table checkpoint, TestComplete finds all the rows and cells, and builds a new table store without complaint.

Recognizing Custom Objects

If you point Object Spy at a DataGridView, it reports that the ClrFullClassName property is System.Windows.Forms.DataGridView.

Now imagine that “Bob” from R&D creates his own version of DataGridView and places it like a grenade in an application you’re testing. Instead of System.Windows.Forms.DataGridView, he names the class CustomGrid.BobsNiftyGrid.

The new “Bob” grid is essentially a DataGridView, but any attempt to create a table checkpoint triggers an error “Unable to retrieve table data for the checkpoint”, and that the object is not supported.

Object Mapping

Object Mapping creates a relationship between class names and supported controls. The class name System.Windows.Forms.DataGridView maps to Winforms DataGridView support. The screenshot below shows the default Object Mapping settings in the project’s properties.

Notice the Derived Classes check box next to the class name. Enabling the check box compels TestComplete to recognize any class based off of DataGridView, including Bob’s grid.

Now TestComplete recognizes the grid and the table store is created without error.

The post TestComplete Object Recognition appeared first on Falafel Software Blog.