Hello guys,
Thank you for your answers,
Finaly I made it run by adding a one second delay between the lines that causes issues.
It works perfectly.
m_essaid wrote:
Hello guys,
Thank you for your answers,
Finaly I made it run by adding a one second delay between the lines that causes issues.
It works perfectly.
Glad that works. Just note that I find using hardcoded delays to be a problem. What if you run your tests one day and 1 second is no longer long enough?
That's why the "Wait" methods mentioned are better. You can set a maximum wait time, say 10 seconds. If the object returns in 1 second, that's all you're wait. But it will also account for situations where it may take 2 or 3 seconds. I'd look into finding a way of implementing those wait functions to make your tests more flexible with regards to performance delays.
Hey Robert,
I'm not sure that the wait method will work, I think that the VCL component is already available.
I think it's due to our access layer. We built a new access layer for our products and I test both old and new programs. Only thoses that work on the new data access layer make the tests fails.
The VCL component, in both cases, are available.
But... you may be right. When I'll adapt other tests I'll try some wait functions.
