Forum Discussion

ramarajak's avatar
ramarajak
Occasional Contributor
7 years ago
Solved

Perfect Test Case some times not running when Queued in Mulitple Test cases

  Test Complete Script some times won't run on bulk test cases but its working fine on single test case.   That Test Case has no Script error and its gave best result when Execute a single test ca...
  • NisHera's avatar
    NisHera
    7 years ago

    Your log file don't give enough clue to determine what went wrong.

    But I suspect running multi test would some how slow down your test machine/environment.  

     

    One thing you could do is increase waiting time for object where it go's wrong and run it again.

cunderw's avatar
cunderw
Community Hero

You're description doesn't clearly explain your issue. You say there is no error but it does not run? What do you mean by Bulk Test Cases? How are you running your tests? What exactly is happening vs what you expect to happen? 

ramarajak's avatar
ramarajak
Occasional Contributor
7 years ago

HI

 

 Kindly take a look of my attached files.. actually bulk test cases means Multiple Test cases to run(if i have to run test cases more than 50). When i do this action some test case which is scriptwise correct and works when execute on single test case but  in  Multiple Test cases queue it doesn't find object.. 

 

Hope you understand my explanation.

 

 

  • NisHera's avatar
    NisHera
    Valued Contributor
    7 years ago

    Your log file don't give enough clue to determine what went wrong.

    But I suspect running multi test would some how slow down your test machine/environment.  

     

    One thing you could do is increase waiting time for object where it go's wrong and run it again.

    • tristaanogre's avatar
      tristaanogre
      Esteemed Contributor
      7 years ago
      NisHera wrote:

      Your log file don't give enough clue to determine what went wrong.

      But I suspect running multi test would some how slow down your test machine/environment.  

       

      One thing you could do is increase waiting time for object where it go's wrong and run it again.

      I agree with NisHera... this could simply be a performance/timing problem.  We have similar situations in our own test runs where a test case runs fine when run solo but fails with similar errors when part of the larger batch.  Your application under test may have all sorts of other background processes and resource consumption that are still running, processing, releasing, being consumed, etc., from previous tests so the performance will run slower.

       

      Put in appropriate wait logic, detection, etc., to detect the object before you attempt to operate on it.