search

bitrise-steplib / steps-virtual-device-testing-for-android

MIT License
22 stars 23 forks source link

Sharding for instrumentation tests #34

Closed geoff-powell closed 2 years ago

geoff-powell commented 5 years ago

So currently you guys support env vars which is great. The issue is if my device list has more then 1 device and i pass the params numShards=2 shardIndex=0 it will only run half my test suite on both devices. Im asking if there is a way to give separate shards to each device.

Example:

Maybe this can be a parameter under the instrumentation tab like there is for Test targets

lszucs commented 5 years ago

Hi @gpowell13,

Nice catch, unfortunately, we do not support test sharding, yet. Please open a feature request on https://discuss.bitrise.io/c/feature-request if there is not one already so that we can contact you once the feature request is triaged.

Let me know if you have any issues with creating the feature request.

Thanks. :)

zawadz88 commented 4 years ago

It would be great to see this feature. Currently, we have to do it ourselves via Environment Variables in Test Setup but this means we run a number of Bitrise builds in parallel. Having a single Bitrise build would mean we had more free agents to use on Bitrise to build other stuff.

bitrise-coresteps-bot commented 2 years ago

Hello there, I'm a bot. On behalf of the community I thank you for opening this issue.

To help our human contributors focus on the most relevant reports, I check up on old issues to see if they're still relevant. This issue has had no activity for 90 days, so I marked it as stale.

The community would appreciate if you could check if the issue still persists. If it isn't, please close it. If the issue persists, and you'd like to remove the stale label, you simply need to leave a comment. Your comment can be as simple as "still important to me".

If no comment left within 21 days, this issue will be closed.

bitrise-coresteps-bot commented 2 years ago

I'll close this issue as it doesn't seem to be relevant anymore. We believe an old issue probably has a bunch of context that's no longer relevant, therefore, if the problem still persists, please open a new issue.