Testcomplete and 64 bit slaves

Hi Shubhangi,

Please clarify the following things:



1.

The scenario passes when tested manually.

2.

the popped page is not found

3.

After reboot, a page for "Password change" pops up.

4. Have you tried adding delays after rebooting the system? You can use the Delay() method for this purpose.

5. Have you tried adding the Refresh() method for the pop-up window's parent object?

6. If you are using name mapping, have you tried using the RefreshMappingInfo method?

Thanks.

Thanks for the reply.

I am not familiar with TC.

The code is written by someone else and I am revamping it now.

I could find answers for some of your questions. However I will look into the code in details to answer remaining questions.



1.  The scenario passes when tested manually.

>>>>Yes. The scenario passes when executed manually.

2. the popped page is not found

>>>>>

3. After reboot, a page for "Password change" pops up.

Did you use the RebootAndContinue method to reboot the system?

>>>>>

4. Have you tried adding delays after rebooting the system? You can use the Delay() method for this purpose.

>>>>Yes.

I tried using delays.



5. Have you tried adding the Refresh() method for the pop-up window's parent object?

>>>>Yes.

6. If you are using name mapping, have you tried using the RefreshMappingInfo method?

>>>>

=================================================

Note :  After reboot, the product runs MgntTool.exe and pops up a window. I can see that window on

screen and can also see the exe running in TaskManager.

However after reboot when TestComplete locks the slave, MgntTool.exe and the correspnding popped page are killed somehow. The exe is not listed in the TaskMAnager.

This works fine on 32 bit OS (XP, win7 and Vista) and fails on 64 bit.

====================================================

function DPPasswordChange()

{

          Log.Message("Loading DP Password Change Window"); 

          Sys.Refresh();

          Delay(5000);

          var me=this;

          var processHwnd=Sys.WaitProcess("MgntTool",30000);

    

      //It is imp that this exists function should appear before the below IF statement

      //Coz Jscript wouldn't even create the function if the contructor returns before the function's declaration

      me.Exists=function()

      {

            return processHwnd.Exists;

      }

      if(!processHwnd.Exists)

      {

        return me;                   =========================>Function returns here for 64bit

    }

      var count=0;

     do{

           Delay(1000);

            me.w1=new

            UIElements.Window(processHwnd,"WndCaption","DISK Protect Password Change",1);

            count++

      }while(!me.w1.Exists() &&

count<30);

     Log.Message("Took less than "+count+" secs to launch");.



      <<<<<Codeto edit the text boxes>>

}

 

Regards,

Hi Shubhangi,

I have some more questions:

1. First of all, please replace the Refresh() method with the Delay() one. That is, the code must contain the following code snippet:

   Delay(5000);

   Sys.Refresh();

2.

However after reboot when TestComplete locks the slave, MgntTool.exe and the corresponding popped page are killed somehow. The exe is not listed in the TaskMAnager.

3. One more suggestion: try switching off all the Open Application plug-ins. For this purpose, select File | Install Extension from TestComplete's main menu and clear the following check boxes:

 * .NET Open Application Support

 * Adobe Flex Controls Support

 * Delphi and C++Builder Open Applications Support

 * Java Open Application Support

 * JavaFX Open Application Support

 * MSAA Open Application Support

 * Microsoft Visual C++ Open Application Support

 * Open Applications Support

 * Qt Library Controls Support Plug-in

 * Qt Library Support Plug-in

 * Silverlight Open Application Support

 * Visual Basic Open Applications

 * Web Testing Plug-in

 * WPF Controls Support Plug-in

Click OK to close the dialog and then click the Save All button to apply the changes.

Does the problem remain? If it doesn't, try switching on the plug-ins in turn to find the problematic one.

Thanks.

Hi Irina,

Here is an answer to your question

2.However after reboot when TestComplete locks the slave, MgntTool.exe and
the corresponding popped page are killed somehow. The exe is not listed in the
TaskMAnager.

Are you running your test using the NetworkSuite project item? Also, could you
please clarify the way the MgntTool.exe application is launched after
rebooting?

This is one of the functionality of the product I am testing. When we create a user with password for this product. We can force that user to change the password on next boot. (just like administrator creates a domain user account and a password for us and We change that password to our own password after logging in)

When I install the product and create a user and Enable the option which says "Force password change after reboot". When product is rebooted under this user, the MgntTool.exe should be started automatically which is responsible for ChangePasswordWindow.

Shubhangi,

As far as I know, the autorun behavior you described is implemented via special Registry keys. TestComplete's RebootAndContinue functionality also uses these keys. Perhaps, TestComplete is launched before the operating system processes the keys responsible for launching your application. In this case, the test script fails to find your process as it simply has not been launched yet. The problem and solution are described in the following technical article on the SmartBear web site:

[url=http://smartbear.com/support/articles/testcomplete/testing-applications-that-require-rebooting/]
Testing Applications That Require Rebooting[/url]

Let us know whether this helps.

Hi Shubhangi,

I replied to you in the thread (http://smartbear.com/forums/forum/post/?mode=singleThread&thread=36172944-48a6-45e9-a557-1d6395f944ad) you had mentioned.

Hi Shubhangi,

As far as I understand, you change the Windows account and TestComplete looses the connection with the ForcePasswordChange window, am I right? If I'm right, I think you haven't closed the session had been opened for the previous user, and TestComplete was opened in a new session, but the ForcePasswordChange window remained open in the session that had not been closed. If it's so, the behavior is correct, as TestComplete can work only with applications that are running in the same session as TestComplete.

As for the verify method, as far as I understand, you mean Host.Verify()? This method doesn't change a user or anything of that kind. The behavior of this method depends on the state of the Automatic logon property. If it's enabled, TestComplete tries to connect to the specified host and creates a session under the specified account. If the session is created, the Verify method returns true. If the logon property is disabled, the method just checks whether the specified session exists. Do you mean the method I described?