Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

be able to block device for future tests #1756

Open
vdelendik opened this issue Jun 24, 2022 · 0 comments
Open

be able to block device for future tests #1756

vdelendik opened this issue Jun 24, 2022 · 0 comments
Milestone

Comments

@vdelendik
Copy link
Contributor

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)

@akamarouski akamarouski self-assigned this Feb 13, 2024
@akamarouski akamarouski added this to the 1.2.8 milestone Feb 13, 2024
@akamarouski akamarouski modified the milestones: 1.2.8, 1.2.9 Feb 21, 2024
@akamarouski akamarouski modified the milestones: 1.2.9, 1.3.10 Mar 17, 2024
@akamarouski akamarouski removed their assignment Jul 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Todo
Development

No branches or pull requests

2 participants