npaisley
StaffUser Profile
Staff
User Widgets
Contributions
Re: the 'keys' option is missing on the list of Method or Property
Hi karenriviam! Is there a specific reason you need to use the Keys method instead of 'ClickItem'? Usually we see that when clicking on a field that already has text in it, so we don't need to send along any key/text, just simply click the text that is already present. Does your test work on playback with 'ClickItem'?Re: In Headless Testing some of the priority values are different compared to regular GUI Testing
Hi Uttham! Reading through our documentation I see it might be related to the type of user-agent being used. We can alter this to help make sure the application reacts the same for each type of browser. From our docs; "If your tested website or web application behavior varies depending on whether your browser is in headless mode or not, for example, some resources are not available in headless mode, you may want to bypass this by overriding the user-agent string sent by your browser. To do this, you can use the --user-agent command-line parameter of Chrome and Edge." Here is the document itself with more information; https://support.smartbear.com/testcomplete/docs/app-testing/web/supported-browsers/headless.html I hope this helps!Re: Unable to connect to BitBar via automation script using appium + NodeJS + WebdriverIO
Hi MrunalCTS! I was able to stand up our WDIO sample without issue unfortunately. Can you tell us what all has been changed in the config file? I also see the 405 is coming back from an NGINX server it looks like. Does your application need to contact a machine that is not publicly available? If so, and you are using NGINX, it might help to investigate using our SecureTunnel tool for local connections; https://support.smartbear.com/bitbar/docs/tunnel/index.html If not, let me know and any more information about the config file, and your test itself. We'll be happy to help.Re: BitBar exploratory testing
Hi praveen_gadupud! While unfortunately this functionality currently doesn't exist, this would make a great feature request! You may submit feature requests for the BitBar platform through the link below; https://community.smartbear.com/t5/forums/postpage/choose-node/true/board-id/BitbarFeatureRequests?source=newTopicBtn Thanks!Re: Appium server error com.testroid.api.APIException: Failed to submit test run! No device model match
Hi nadavgivoni! Normally instead of providing the name of the device in your capabilities, you would provide the Device ID. You may obtain this by using an ADB command 'adb devices' in a CLI. Once you have ADB setup, run that command and take the ID for your device and replace your 'deviceName' capability with this ID. This is most likely the issue. For instance, to connect to my Galaxy S7, I use the below basic capabilities after retrieving the ID from ADB; { "platformName": "android", "deviceName": "R52RC0E21RF" } I hope this helps!Re: Unable to connect Appium Inspector(Web version) to session with Bitbar device
Hi Jasodhara! Unfortunately Appium Inspector 2.0 is not supported by BitBar, but 1.0 is. You may obtain this through the link below; https://github.com/appium/appium-desktop/releases/tag/v1.22.0 Also remember that you will need to connect to BitBar's server, not your local one. So the remote host and path will be BitBar's. You may find all the information for these servers in the capabilities configurator; https://cloud.bitbar.com/#public/capabilities-creator I hope this helps!
