Forum Discussion
tristaanogre
14 years agoEsteemed Contributor
Let's start looking at your actual test and test code to see if this is something that needs to be solved in code. Let's do two thing:
1) As I suggested above, you might want to try "watching paint dry". Set up the task to auto trigger and sit back and watch and see what happens in case something odd is happening that you're not obvserving in your manual runs
2) Could you post the relevant script code or, if you're using a keyword test, a screen shot showing the keyword test with the Operation, Object, and Parameters fields clearly visible?
That would help a lot with debugging. My suspicion, though, is the same that I mentioned above... that somehow the relevant window is being masked or made unavailable due to some sort of security issues on the box in question that is different between having the automatically executed task versus a manually triggered one.
1) As I suggested above, you might want to try "watching paint dry". Set up the task to auto trigger and sit back and watch and see what happens in case something odd is happening that you're not obvserving in your manual runs
2) Could you post the relevant script code or, if you're using a keyword test, a screen shot showing the keyword test with the Operation, Object, and Parameters fields clearly visible?
That would help a lot with debugging. My suspicion, though, is the same that I mentioned above... that somehow the relevant window is being masked or made unavailable due to some sort of security issues on the box in question that is different between having the automatically executed task versus a manually triggered one.
Related Content
- 3 years ago
- 5 months ago
Recent Discussions
- 2 days ago
- 2 days ago
- 6 days ago