Forum Discussion

ProVI_Bollig's avatar
ProVI_Bollig
Occasional Contributor
2 years ago
Solved

Test Case failed caused by timeout but shows success in the log

Hello Community,

We set the timeout for each test case to be 5 minutes. We expect the test case to fail and marked as an error when the duration is longer than the timeout so that we can rerun the test case. The test execution summary correctly shows the test as having failed and timed out. However, it is logged as "success" in the log detail window, and the test case was also not rerun.

 

What could the reason be for this behavior?

Could anyone help us?

many thanks:)

 

Test Results
  • MadGrb's avatar
    MadGrb
    5 years ago

    Finally I write a script to Click on nested Menu that is not recognized with TC-Engine.

     

            def SelectContextMenueStrip(cls, Contain_0 = '', Contain_1 = ''):
    
                try:
        
                        Index_0 = 0
                        Index_1 = 0
                        Delay(50)

                        ContextMenuStrip = Aliases.JTL_Wawi.ContextMenuStrip
                
                        Height = ContextMenuStrip.Height
                        Width = ContextMenuStrip.Width
                        Count = ContextMenuStrip.get_Items().Count
                        IndividualHeight = Height / Count
    
                        for Index_0 in range(0,Count,1):
                                Item = ContextMenuStrip.GetItemAt(Width/2, IndividualHeight * Index_0 )
                                if Item != None:
                                        if ContextMenuStrip.GetItemAt(Width/2, IndividualHeight * Index_0 ).Text.OleValue == Contain_0:
                                                ContextMenuStrip.Click(Width/2, IndividualHeight * Index_0) 
                                                 
                                                if Contain_1 != '':
                                                        ContextMenuStrip_1 = Aliases.JTL_Wawi.ContextMenuStrip.activeDropDowns_2.Item[0]
                                                        
                                                        Height_1 = ContextMenuStrip_1.Height
                                                        Width_1 = ContextMenuStrip_1.Width
                                                        Count_1 = ContextMenuStrip_1.get_Items().Count
                                                        IndividualHeight_1 = Height_1 / Count_1  
                                                        
                                                        for Index_1 in range(0,Count_1,1):
                                                                Item_1 = ContextMenuStrip_1.GetItemAt(Width_1/2, IndividualHeight_1 * Index_1 )
                                                                
                                                                if Item_1 != None:
                                                                        if ContextMenuStrip_1.GetItemAt(Width_1/2, IndividualHeight_1 * Index_1 ).Text.OleValue == Contain_1:
                                                                                MouseX = ContextMenuStrip_1.Left
                                                                                MouseY = ContextMenuStrip_1.Top
                                                                                Sys.Desktop.MouseDown(VK_LBUTTON , MouseX + Width_1/2, MouseY + IndividualHeight_1 * Index_1)
                                                                                Sys.Desktop.MouseUp(VK_LBUTTON , MouseX + Width_1/2, MouseY + IndividualHeight_1 * Index_1)
                                                        Index_1 += 1
                                Index_0 += 1
                                                            
                        
                except Exception as exp:
                        Log.Message('SelectContextMenueStrip - type:' + str(exp))

     

     

    I use mouse position to click on desktop, Enjoy it 😉

     

4 Replies

Sort By
  • ProVI_Bollig's avatar
    ProVI_Bollig
    Occasional Contributor
    2 years ago

    Hello rraghvani,

    I think I have found the problem.

    The difference in results between the summary and the log details is caused by the custom event handler written by us. 

    With your help, we noticed that it was not a problem of TestComplete itself!

    Thank you so much!

  • rraghvani's avatar
    rraghvani
    Icon for Champion Level 3 rankChampion Level 3
    2 years ago

    How have you defined the "timeout"?

     

    "The test execution summary correctly shows the test as having failed and timed out" - I only see pass?

     

    Why do you need to timeout for 5 minutes, that seems to be very long?

    • ProVI_Bollig's avatar
      ProVI_Bollig
      Occasional Contributor
      2 years ago

      Hi 

      Thanks for the reply.

      What I posted is the screenshot of the log details window. The timeout is shown by the large Time diff on termination. Here is the screenshot of the execution summary. As said, the test case terminated by timeout is marked as "success" in the details log but as "error" in the summary. The latter is what we expect to see in the details log as well.

       

      The 5 minutes timeout is just a standard for each case in the execution plan so that we know something is stuck and it should be stopped. Some test cases take quite a long time, so we assume it is a safe value.

  • rraghvani's avatar
    rraghvani
    Icon for Champion Level 3 rankChampion Level 3
    2 years ago

    Test case "Case2" is showing a failure in the Test Execution Summary Report. However, in the Log Details, it's showing as Pass?

     

    I thought it was relating to how the execution plan was structured, but I'm not able to reproduce this issue.