ContributionsMost RecentMost LikesSolutionsRe: How to view developer console in browser test? Developer console is available exclusively for desktop browser testing in BitBar Live Testing. You can access it by clicking the [DEV] icon located on the device navigation menu. Re: Unable to connect to local host It seems it needs a proper support ticket Re: No devices appear to be available That's the best way :) It's worth the money Re: No devices appear to be available Since yesterday (12/10/24), gmail.com domain was restricted from using BitBar. Please, use your corporate email to continue testing. Re: How to inject local image file in device hi katarzynar unfortunately this functionality was pushed back to address other needs. It's still on our radar. I'm curious about your use case of image injection. Would you be opened to have a chat around that? Re: BitBar - How to fail the entire test run if test cases failed hey arunbharath in order to set device session status to failed, you can use POST broker endpoint *BROKER_ADDRESS*/sessions/*ID*, and pass parameter "state = FAILED" in the body. Endpoint support only application/x-www-form-urlencoded f.i. for eu mobile hub, it looks like this POST eu-mobile-hub.bitbar.com/sessions/*id* {state = FAILED} Re: Does Bitbar support Playwright with Cucumber? hi unfortunately, Playwright is not yet supported in BitBar. But i'm happy to jump on a call to discuss that or discuss this on DM Best Kuba, Product Owner Re: BitBar Parallels max usage Hey Wim Let's discuss this! Have just sent you a mail. Re: Unable to connect Appium Inspector to session with Bitbar device Hi Denis there're two parts to your problem: 1. Appium Inspector seems to require (or adds on it's own) "source" capability, which is not supported. Good news is, incoming release (December 5th) brings this support. 2. The way you create keys for capabilities isn't correct. W3C requires you to preffix to vendor specific capabilities, which "appium:" for appium specific capabilties and respectively "bitbar:" to bitbar ones. However you added "appium:" to bitbar capabilities. You should remove that and leave just "bitbar_XYZ" One more thing that's worth mentioning (if you'd like to switch entirely to W3C format), which is Appium Inspector inherent problem, that we discovered: Appium Inspector does internal mapping/replacement of capabilitiies when you use W3C format with bitbar specific capabilities to incorrect ones. Meaning: don't use "bitbar:options:" object, just stick to "bitbar_XYZ" format (they way you do, but remember to remove "appium:", what I explained eariler) enjoy testing! Re: How to start subscription in BitBar Hi Isravel if you want to start your trial, follow this link https://smartbear.com/product/bitbar/free-trial/ if you are existing user, then just use subscription page https://cloud.bitbar.com/#user/subscriptions In any other case best approach would be to contact support