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.**** ...
Forum Discussion
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.
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.