From version < 4.1 >
edited by Jonathan Rubiero
on 2018/05/25 14:39
To version < 5.1 >
edited by Jonathan Rubiero
on 2018/05/25 14:45
< >
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -Troobleshouting
1 +Troubleshooting
Content
... ... @@ -4,17 +4,11 @@
4 4  
5 5  It may be possible that a Keyword execution //**times out**// producing this kind of error when executing it :
6 6  
7 -[[image:1527258710359-314.png||width="1389" height="643" alt=""]]
7 +[[image:1527258710359-314.png||height="643" width="1389"]]
8 8  
9 9  Several reason could explain this behavior :
10 10  
11 -* by default, when you create a Keyword in STEP, its maximum execution time is set to 180 seconds. If you expect your Keyword execution to be longer than this 180 seconds, you have to adjust this value. For this, edit your Keyword and modify the "Call timeout" setting :[[image:1527259022785-273.png||width="1918" height="683" alt=""]]
11 +* by default, when you create a Keyword in STEP, its maximum execution time is set to 180 seconds. If you expect your Keyword execution to be longer than this 180 seconds, you have to adjust this value. For this, edit your Keyword and modify the "Call timeout" setting :[[image:1527259022785-273.png||height="683" width="1918"]]
12 12  
13 -
14 -
15 -
16 -- si c'est anormal: reproduire en unitaire en recopiant les inputs du keyword et faire analyser par le développeur du keyword
17 -
18 -- s'il ne reproduit pas, il faut tenter de reproduire directement sur l'agent et si ça n'est pas reproduit à tous les coups essayer plusieurs fois et surveiller
19 -
20 -- en option, le développeur peut ajouter par lui même des traces optionnelles (screenshots en attachment à chaque étapes, informations supplémentaires ajoutées en output à chaque étape, prendre des mesures start/end pour savoir quelle étape prend du temps, etc).
13 +* If having such a long run is not expected, you should give the Keyword inputs to the developer in charge of its development and ask him to analyze what the problem is. Furthermore, he could add some traces to the Keyword code which could help understanding what the problem is (screenshot in attachments during critical Keyword step, additional information added to the Keyword output, adding some extra time measure etc...)
14 +* If the developer cannot reproduce the issue, you should try to reproduce the issue directly in STEP several times and analyze the logs and the application behavior.
Copyright © exense GmbH
v1.0