Forum Discussion

shubhangi's avatar
shubhangi
Contributor
13 years ago

NetworkSuite->AutomaticLogon for 64 bit slave


Hi,


I am using Networksuite for running the tests on different
slaves in parallel.


On slaves, I have a windows user "Admin/Password".


On Network Suites- Host has following properties. UserName -
Admin, Pwd - Password and Automatic Login - True.


I execute a test case, the actionAfterRun is saReboot. This
works fine.


The next test is supposed to work on the dialogs which pops
uo automatically after reboot.


At this stage,  Host.Verify succeeds. But Testcomplete does
not see the dialog . We can see them if we manually log in to windows (Admin/Password)
on slave.


Ideally, if the AutomaticLogon is enabled for host (networksuite
host property), TestComplete should create a user session which should be able
to see the dialogs.


Looks like Testcomplete's automatic logon is trying to log
in with some other user on win7(64).


I am running TestComplete/TestExcute 8.60 version. Any help would be greatly appreciated.


Thanks,


Shubhangi


  • shubhangi's avatar
    shubhangi
    Contributor
    13 years ago
    Sorry for late reply.

    The problem I mentioned in the post is because of a bug in software, I am testing.

    Somehow the dailog is not seen through RDP.

    Hence Testcomplete could not see it.



    Shubhangi

  • AlexanderM's avatar
    AlexanderM
    Icon for Staff rankStaff
    13 years ago

    Hello Shubhangi,





    When you set the actionAfterRun parameter to saReboot, the slave computer will be rebooted after Task execution. At that, no user will be logged in automatically after the reboot. So, could you clarify your scenario:





    Are you configuring the AutoLogon feature of Windows on the Slave computer from your Slave test (writing the needed Registry entries) before the Task is completed?





    Or do you have one more Task (with the Automatic Logon option enabled) configured to run on the same Slave PC, and your Master test waits for the host to become available after reboot (doing verification in a loop), and then starts the next Task?





    Of are you implementing some different approach?





    Also, let me know what exactly happens when a test runs on the Slave computer after a reboot. If it is failing, could you post the exported Test Log here? Or can you send it to Support? This should help us better understand what is going on, and help you resolve it.





    Thanks!
  • AlexanderM's avatar
    AlexanderM
    Icon for Staff rankStaff
    13 years ago

    Hi Shubhangi,


     


    Thanks for sharing your findings!


    Sounds like a good rule for QA Engineers - "Tests are used to fail because of bugs in the tested app, so check this assumption first" :)


     


    Good Luck with your testing!

  • shubhangi's avatar
    shubhangi
    Contributor
    13 years ago
    Yes. You are right :)

    Would like to mention one more point, as an automation engineer always check the functionality manually and also check if it works fine through RDP to be automated using TC.

    In my case, functionality was verified manually. However the dialog was not visible if you are logging in remotely.

    This leads to a question, how do we use TC when few dialogs/processes are not accessible via RDP for security reasons ?



    Shubhangi
  • AlexanderM's avatar
    AlexanderM
    Icon for Staff rankStaff
    13 years ago

    Shubhangi,


     


    It would be interesting to learn more about those dialogs, and about the tested app's behavior when using RDP.


     


    In a general situation, if the behavior is expected to be different via RDP, the functional tests are expected to take this specifics into account. However, if those dialogs are not visible through RDP due to security reasons, I wonder how a human would perform the same scenario... Could you clarify?