Sleep utility function

[forcedotcom]

Sleep utility function

[esalman-sfdc]

I am wondering how can this be achieved without making the tests flappy/brittle. For example, for selenium/webdriver as well it has become a fairly standard best-practice to wait for something vs sleeping as a result of test owners getting burnt by flaky results :)

As you pointed out, if all components have locker enabled (v.40+) its easier to do (by letting the library add some marker). Is there anything else that the component under test do you could wait on (directly or via a test-wrapper component)?

Basically I am worried that providing a utility like sleep (well versed users like yourself may not be impacted as much) may result in adoption of an anti-pattern (one that results in false positives when it comes to failures).

What do you think?

[keirbowden]

I take your point about the fact that sleeping is brittle, but I'm also loathe to set attributes solely for the purpose of indicating to tests that they can proceed. Interesting that you bring up Selenium as that was the same direction I was coming from. I'll have a bit more of a think about it over the next few days.

[keirbowden]

I'll cave on this one - I can't come up with a good rebuttal to your reasons :)