GXtest Troubleshooting

Unofficial Content

On this page, you can find some common errors related to GXtest objects and how you can fix them quickly. 

Build error: The type or namespace name 'SdtUITest' could not be found

This error happens with GXtest versions prior to (GeneXus 16 Upgrade 10).

Solution: force a rebuild of the UITest external object. This can be achieved by

a) modifying the object itself or

b) using the option Test -> Rebuild All Tests.

Error: Could not set Procedure “Runner” as main

A possible cause of this error could be that a KB is being opened with an older version of GXtest.

Solution: Delete Runner object. When you execute a test, it will be created again but with the appropriate version.

Testing object or related gives build error

These cases could be a typical error that some objects need to be rebuilt. Test objects are not built in a Rebuild All operation because they are not called by any Main object (except some user change it), so the option Rebuild All Tests forces to rebuild test objects and their references.

Solutions: there are two options:

a) Modify the object so is automatically rebuilt by GeneXus in the next execution

b) Run the option Test -> Rebuild All Tests.

Running web UI tests on Jenkins or similar

In order to web UI tests work properly, browsers must be opened by the CI server. That is because commands that involve focus over elements (like typing) cannot be performed in some browsers, depending on the particular case.

For example, if the CI server is executed as a windows service it must be enabled the setting "Allow service to interact with desktop"