You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
from time to time we know that this particular device is not applicable for tests execution anymore, mostly due to the infra issue aka out of space, broken wi-fi, blocked apk install etc.
for the cases when we can block only for this particular we need IDriverPool.block(Device device) method.
and maybe one more with ability to decrease thread_count IDriverPool.block(Device device, boolean limitThread)
After running above method we might inspect capabilities and if device is listed, just remove it from the list. If not, we might deliver new feature for the grid as well, aka deviceNameBlocked=....
Ideally we have to analyze thread_count or data_provider_thread_count and do --1 if possible. Still unclear howto block execution in this case as TestNG doesn't allow to manipulate by threads count at run rime, maybe just fake process running like sleep in these thread(s)
The text was updated successfully, but these errors were encountered:
from time to time we know that this particular device is not applicable for tests execution anymore, mostly due to the infra issue aka out of space, broken wi-fi, blocked apk install etc.
for the cases when we can block only for this particular we need
IDriverPool.block(Device device)
method.and maybe one more with ability to decrease thread_count
IDriverPool.block(Device device, boolean limitThread)
After running above method we might inspect capabilities and if device is listed, just remove it from the list. If not, we might deliver new feature for the grid as well, aka
deviceNameBlocked=...
.Ideally we have to analyze thread_count or data_provider_thread_count and do
--1
if possible. Still unclear howto block execution in this case as TestNG doesn't allow to manipulate by threads count at run rime, maybe just fake process running like sleep in these thread(s)The text was updated successfully, but these errors were encountered: