jakubczop
StaffJoined 2 years ago
User Profile
Staff
User Widgets
Contributions
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}84Views0likes0CommentsRe: 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!375Views1like0CommentsRe: 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 support149Views0likes0Comments