Using the Desktop object is prohibited when running in non-interactive mode

4 posts, 0 answers
  1. Martin Lalonde
    Martin Lalonde avatar
    3 posts
    Member since:
    Jan 2010

    Posted 30 Mar 2015 Link to this post

    Hi,

    I've come across this issue when running tests on our build server :

    ArtOfTest.WebAii.Exceptions.UnsupportedNonInteractiveOperationException : Using the Desktop object is prohibited when running in non-interactive mode. Follow the link for more information: http://docs.telerik.com/teststudio/user-guide/knowledge-base/test-execution/no-tests-execute-on-locked-machine.aspx

    I didn't tried all the solutions using Remote Desktop sessions and VNC yet.  

    In the documentation page above, it is mentioned : "Any test that requires moving the mouse or sending key strokes requires an unlocked desktop."  So, what I'd like to know is what are the methods and objects I should avoid when not running on interactive mode.  

    Regards,
    Martin
  2. Humberto
    Humberto avatar
    8 posts
    Member since:
    Mar 2012

    Posted 01 Apr 2015 in reply to Martin Lalonde Link to this post

    Ooh, excellent question Martin.  I too am curious.  Especially since given our environment where IT security has really been tightened down in the last year or so...this is quite important!

    The IT folks would scream "hell no" if we told them we need a box running 24/7 where a user is permanently logged in and the browser can't be minimized and has to be up and visible and running...and oh yeah, can we also have a dummy username and password as well that all the developers can share to get into this box...

    Telerik folks, I am curious if this is due to simulating user interactions with javascript vs. using OS-level native events that would employ the OS Desktop, Mouse and Keyboard objects?
  3. Humberto
    Humberto avatar
    8 posts
    Member since:
    Mar 2012

    Posted 01 Apr 2015 in reply to Martin Lalonde Link to this post

    Ooh, excellent question Martin.  I too am curious.  Especially since given our environment where IT security has really been tightened down in the last year or so...this is quite important!

    The IT folks would scream "hell no" if we told them we need a box running 24/7 where a user is permanently logged in and the browser can't be minimized and has to be up and visible and running...and oh yeah, can we also have a dummy username and password as well that all the developers can share to get into this box...

    Telerik folks, I am curious if this is due to simulating user interactions with javascript vs. using OS-level native events that would employ the OS Desktop, Mouse and Keyboard objects?
  4. Ivaylo
    Admin
    Ivaylo avatar
    750 posts

    Posted 02 Apr 2015 Link to this post

    Hello Martin,

    I guess it is quite clearly explained that any test that requires moving the mouse or sending key strokes requires an unlocked desktop. Telerik tests are not the only types affected by this Windows limitation. You will find this is a general problem with any tool that performs UI testing.

    Our tests against HTML-based web applications frequently can work on a locked machine because most test steps don't use the mouse or keyboard. Instead they are able to inject Click or Select events against the element in question (e.g. a button or drop-down select). Unfortunately Silverlight and WPF applications do not allow us to inject these events. We have to simulate system wide mouse moves, clicks, and key presses instead.



    Regards,
    Ivaylo
    Telerik
     
    Quickly become an expert in Test Studio, check out our new training sessions!
    Test Studio Trainings
     
Back to Top