# Virtual Device Testing and Wi-fi

**URL:** <https://discuss.bitrise.io/t/virtual-device-testing-and-wi-fi/9294>\
**Category:** Question & Answer\
**Tags:** android, emulator\
**Created:** [June 13, 2019, 2:46pm UTC](https://discuss.bitrise.io/t/virtual-device-testing-and-wi-fi/9294 "2019-06-13T14:46:52Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![dicksson.oliveira](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.bitrise.io/dicksson.oliveira/32/2397_2.png) [@dicksson.oliveira](https://discuss.bitrise.io/u/dicksson.oliveira)\
**Post date:** [June 13, 2019, 2:46pm UTC](https://discuss.bitrise.io/t/virtual-device-testing-and-wi-fi/9294/1 "2019-06-13T14:46:52Z")

</div>

Hey guys,

I have a couple integration tests that use Wi-Fi. The [Android Emulator User guide](https://developer.android.com/studio/run/emulator.html#wi-fi) states that emulators that use an AVD with API level 25 or higher provides a simulated Wi-Fi access point, so I changed the device configuration on the VDT step, but no luck. While they work in a local emulator, they fail in Bitrise.

Is this a limitation of the VDT step, or some issue with Firebase Test Lab?

Thanks in advance!

---

<div class="post-metadata">

**Author:** ![koral](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.bitrise.io/koral/32/357_2.png) [@koral](https://discuss.bitrise.io/u/koral)\
**Post date:** [June 13, 2019, 6:44pm UTC](https://discuss.bitrise.io/t/virtual-device-testing-and-wi-fi/9294/2 "2019-06-13T18:44:28Z")

</div>

Devices on FTL used by VDT are not emulators.  
What problem do you want to solve?

---

<div class="post-metadata">

**Author:** ![dicksson.oliveira](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.bitrise.io/dicksson.oliveira/32/2397_2.png) [@dicksson.oliveira](https://discuss.bitrise.io/u/dicksson.oliveira)\
**Post date:** [June 13, 2019, 7:08pm UTC](https://discuss.bitrise.io/t/virtual-device-testing-and-wi-fi/9294/3 "2019-06-13T19:08:59Z")

</div>

I see. Some of our tests use Wi-Fi capabilities, so without it, they fail. I can ignore them for now, but it may be a limitation for tests of this nature (I also had some failing tests that use the FusedLocation API, but it seems that the device’s location setting is set to battery saving mode).

---

<div class="post-metadata">

**Author:** ![bitce](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.bitrise.io/bitce/32/1639_2.png) [@bitce](https://discuss.bitrise.io/u/bitce)\
**Post date:** [June 17, 2019, 12:44pm UTC](https://discuss.bitrise.io/t/virtual-device-testing-and-wi-fi/9294/4 "2019-06-17T12:44:24Z")

</div>

Hi @dicksson.oliveira!

@koral, is completely right, this is one of the highest requested features for FTL but they do not support Bluetooth/Wi-Fi connection at the moment.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex016/uploads/bitrise/original/2X/d/d901cf2aad020f2dd11918afc89ec2089bb87b35.png) [@system](https://discuss.bitrise.io/u/system)\
**Post date:** [July 17, 2019, 12:44pm UTC](https://discuss.bitrise.io/t/virtual-device-testing-and-wi-fi/9294/5 "2019-07-17T12:44:27Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.