Forum Discussion

AssiaDerias's avatar
AssiaDerias
Occasional Contributor
9 years ago

Application Stopped responding

Hi I realized a web project that contains 109 test with Keyword tests and  sripting, each tests work fine,  but when I run the all together, and before the execution ends,  The system stops and disp...
Colin_McCrae's avatar
Colin_McCrae
Community Hero
9 years ago

I'm pretty much in agreement with tristaanogre in broad terms.

 

You mention: "But  in all my test I have  only  -The RUN Browser- activated in the first Test (Test 1)and -Close Browser- at the end (test 109)"

 

So does this mean you start the browser in test 1 ..... do all sorts of things/tests with it in test 2 - test 108 .... and then close it again in test 109? And test 108 is now throwing an error? (When you run them all, but it's OK on it's own.) 

 

Which means you have 106 possible candidates. Namely, tests 2 - 107. One of them is doing something which means test 108 can't run. Being the test before it, I guess 107 is the prime candidate. But it could be any of them to be honest. You need to look into the object that's throwing up the problems and see if you can work out which of your previous tests is affecting it.

AssiaDerias's avatar
AssiaDerias
Occasional Contributor
9 years ago

Hi;

Finally i have found solution of my bug;

It's matter of web page, i activate the navigate browser of the test number 108 and all work fine

But i  noticed that as the execution progress to the end the tests become more slow, and i don't know Why!!

 

Thank you very match for your help and attempt to resolve my  problem

 

PS: i would pass a certification Exam  of test complete for beginner/or intermediate,  what dou you advice me?

Thank you in advance

  • Colin_McCrae's avatar
    Colin_McCrae
    Community Hero
    9 years ago

    So test 108 was starting and expecting to find the browser at a certain page/point? Which is not where test 107 was leaving it.

     

    Sounds about right.

     

    With automated testing, a lot of it comes down to control. A human tester will look at the site before starting a test. If it's not in the right place, they notice this (you'd hope) and put it in the correct state before they start.

     

    Automated tests .... won't. They're completely dumb. They only do what you tell them. Start it in the wrong place? It won't know and will plough merrily on making a big old mess until it ends or crashes.

     

    Hence why ALL automated tests should have well controlled startup and teardown routines.