This project is read-only.

Remote Desktop GUI Test Problems

Aug 17, 2009 at 4:45 PM

We are currently using White to run our GUI tests on a server which our team accesses using Windows Remote Desktop.  When we run our GUI tests locally (on multiple development machines), all of the tests pass.  However, we find the GUI testing with Remote Desktop very inconsistent.  Sometimes the same test will fail, and if you run it again it will pass.  But most of the time, tests will pass on our local machines, but fail on the remote machine.  This is occurring on approximately 20% of our tests.

Has anyone tried doing GUI testing with White via Remote Desktop?  Any ideas on the issues with consistency?

Aug 18, 2009 at 5:58 PM

Using with Continuous Integration

Aug 18, 2009 at 7:48 PM

Based on the article from the link in your reply, it looks like the only issue with Remote Desktop is that the screen will lock.  However, this is not the problem in our case.  We can watch the tests on the Remote Desktop screen, and they run differently.  Here's a specific example:

myGrid.Rows[0].Cells[0].Value = "MyText1";
myGrid.Rows[1].Cells[0].Value = "MyText2";

The previous code consistently executes correctly on a local development machine. The complete text "MyText1" is placed into (0,0), and "MyText2" is placed into (1,0).

However, when this code executes on our server (which we access via Remote Desktop) sometimes the complete text is not entered.  Instead of the complete text, we might only see "MyTex" in (0,0), and "MyT" in (1,0).  It seems like White is executing the next line of code before the screen has finished entering the text from the current line.

Please let me know if I can give you any more information, or if you have any ideas.

Sep 4, 2009 at 2:25 AM

if you have the source code, you can checkout from codeplex's svn.

In the class TableCell change:



keyboard.PressSpecialKey(KeyboardInput.SpecialKeys.TAB, actionListener);