I am trying to do low-level UI test automation similar to one described here:
To test a method that opens a message box, I call it from a different thread and use win32 API to click the message box away.
The test passes in nunit console, but fails in Team City. When running in nunit console, I am logged into my computer
and can watch the message box physically appear on the screen and then automatically disappear.
And in Team City everything runs "on the background", and the only information I get back is that the message box is not found.
Is there a better way to integrate UI testing into Team City? Is there a setting that would allow me to do this?
Thanks in advance. Alina.