Forum Discussion

joffre's avatar
joffre
Regular Contributor
14 years ago

TestComplete executing wrong script file

I'm executing my script A but TestComplete is running my script B. The two scripts doesn't have any equal property.



One is Aliases.Fpw_Admin.**** and the other is Aliases.FolhaCalc.**** 



I've already restarted TestComplete and my computer, but still not working properly.



What should I do?

11 Replies

  • tristaanogre's avatar
    tristaanogre
    Esteemed Contributor
    14 years ago
    How are you running the test?  If you're running the project, then TestComplete will execute whatever test(s) is/are listed in the test items.
  • joffre's avatar
    joffre
    Regular Contributor
    14 years ago
    I know that.



    I am right clicking my script and selectin "Run Current Routine".



    This is the sub that I am running:

    ''CRIAR BASE

    'USEUNIT ExecutarScripts



    ''CONFIGURAR

    'USEUNIT FPW_Configurar_Admin



    ''FOLHA

    'USEUNIT CC_ExecutarScripts

    'USEUNIT ME_ExecutarScripts

    'USEUNIT Executar_Todos_os_Scripts 



    ''RH

    'USEUNIT TG_ExecutarScripts

    'USEUNIT CS_ExecutarScripts     
    Sub ProjetoFull

        Call ExecutarScripts

        Call Configurar_String_Conexao

        Call ScriptsCC

        Call ScriptsME

        Call Executar_Todos

        Call ScriptsTG

        Call ScriptsCS

    End Sub


     






    The script that is being initialized is inside "ScriptsCC".





    Editing:



    I've attached a screenshot of my running script. This "Form1" doesn't exist in "ExecutarScripts" or "Configurar_String_Conexao".

  • tristaanogre's avatar
    tristaanogre
    Esteemed Contributor
    14 years ago
    Without knowing what's in your individual script calls, I cannot comment as to why it's running the wrong tests.  This sounds like something that you'll need to debug in your code.  Drop a breakpoint on that line for ScriptCC and follow through with a Step Into and go through until you find where the problem is.
  • joffre's avatar
    joffre
    Regular Contributor
    14 years ago
    So I'll do it easier.



    I'm running the script "ConfigFpwAdmin.txt" (attached as a zip file). It doesn't have any Form1 object but TestComplete looks for it. I'm running just the script attached. I right clicked it and selected the same 'Run Current Routine' option.



    Is it some bug?



    I'll restart my machine again to try it again.
  • tristaanogre's avatar
    tristaanogre
    Esteemed Contributor
    14 years ago
    What is determining that TestComplete is looking for Form1?  You are correct, there is no Form1 in this script.  However, you are referencing Aliases which reference back to NameMapping.  In the NameMapping tree for a number of your aliased components, is there any reference to something called Form1?



    Again, your best bet is to drop a break point on the first line of that routine and step through it to see where the problem is.  



    Without your application here that I can run or the project that you're running it in, I cannot debug this for you, unfortunately.



    Do you have any event handlers defined that, upon starting a test, check for a form?
  • joffre's avatar
    joffre
    Regular Contributor
    14 years ago

    First of all, I'm very gratefull for all your help Robert, and I know that if it was possible you would do more than you already do. But this problem is making me crazy! ( LoL )


    The Aliases object that I'm using on my script, as you might saw is "Aliases.FPw_Admin" which was set to a variable named FrmAdmin. In the NameMapping tree of this object there is no Form1 object (attached, I've openned all the options and looked one by one). But the Aliases object used on all the other scripts has this Form1 object.


    I executed this same script before 12pm (04:25pm now) and it was working fine. I didn't edit this. No one did.


    I dropped a breakpoint on the script that is beeing called but it never goes there. It looks for Form1 but it doesn't find it.

  • tristaanogre's avatar
    tristaanogre
    Esteemed Contributor
    14 years ago
    I see in your code that you have a USEUNIT that is referencing a unit called ExecutarScripts.  But then you're also calling a subroutine called ExecutarScripts.  As a general rule of thumb, it's a bad idea to name functions the same name as the unit name.  If you need to do so, you do need to specify the format UnitName.RoutineName.



    While you may not have edited this particular set, it's possible that it's getting "lost" in this area.  This is just a guess, mind you, so I can't guarentee this is the answer.



    Another thing to try:  Left click in the routine that you are wanting to run and then right click in the same routine and select "Run Current Routine".  I don't expect so, but it might be possible that it thinks that there's some other routine currently selected when it tries to "Run Current Routine".



    Another thing to check:  When you get that "waiting for Form1" message and it fails to find Form1, it most likely logs an error message in your test log.  Double-click on that error message line and you'll be taken straight to the line that called that Form1 so you should see where it got called.  Also, on that error message, you should see a Call Stack tab in your log.  That will show you not only the unit that called that code but the stack trace of the units that called THAT unit and so on so you can trace back to what's getting called.
  • joffre's avatar
    joffre
    Regular Contributor
    14 years ago
    I see in your code that you have a USEUNIT that is referencing a unit called ExecutarScripts.  But then you're also calling a subroutine called ExecutarScripts.  As a general rule of thumb, it's a bad idea to name functions the same name as the unit name.  If you need to do so, you do need to specify the format UnitName.RoutineName.



    While you may not have edited this particular set, it's possible that it's getting "lost" in this area.  This is just a guess, mind you, so I can't guarentee this is the answer.




    That was a misunderstood. The script name is different of the function's name; I just typed wrong.



    Another thing to try:  Left click in the routine that you are wanting to run and then right click in the same routine and select "Run Current Routine".  I don't expect so, but it might be possible that it thinks that there's some other routine currently selected when it tries to "Run Current Routine".




    I've tried that too, sadly it didn't work.



    Another thing to check:  When you get that "waiting for Form1" message and it fails to find Form1, it most likely logs an error message in your test log.  Double-click on that error message line and you'll be taken straight to the line that called that Form1 so you should see where it got called.  Also, on that error message, you should see a Call Stack tab in your log.  That will show you not only the unit that called that code but the stack trace of the units that called THAT unit and so on so you can trace back to what's getting called.




    I've tried to double-click the error message but it didn't take me anywhere, and the Call Stack page is blank. After two attempts to find Form1 my script started to run the right script.



    I've attached a screen of my screen (!!).

    Take a look at the .zip file too please.
  • tristaanogre's avatar
    tristaanogre
    Esteemed Contributor
    14 years ago
    Ah... and I think then I know why break points aren't helping you... if your breakpoint isn't stopping and your call stack is empty, that usually means you don't have the MS Script debugger installed as documented http://smartbear.com/support/viewarticle/11360/



    In the meantime, I'm wondering if there isn't some event you have set up that is called OnStartTest.  Go to your Events in TestComplete and see if there is an event handler added to the OnStartTest event and, if so, what code is being executed there.




  • joffre's avatar
    joffre
    Regular Contributor
    14 years ago
    Ah... and I think then I know why break points aren't helping you... if your breakpoint isn't stopping and your call stack is empty, that usually means you don't have the MS Script debugger installed as documented http://smartbear.com/support/viewarticle/11360/




    Actually I do have the debugger installed. I debug my script many times to confirm  if a variable is receiving the value that I want it to receive. The CallStak is only empty in this two cases (see the picture attached).



    In the meantime, I'm wondering if there isn't some event you have set up that is called OnStartTest.  Go to your Events in TestComplete and see if there is an event handler added to the OnStartTest event and, if so, what code is being executed there.




    I've just checked Events > General Events. I'm not familiar with this page, but I think there is nothig set up on it (picture attached either).



    ---



    Thank you one more time Robert...!