Contributions
Re: the 'keys' option is missing on the list of Method or Property
Hikarenriviam! 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'?698Views1like1CommentRe: Tested Apps folder question and Local Appium Server Android Mobile
Hirpfaucher1! This is correct, you may now launch a connection to a device without being forced to provide an application. If you do wish to provide one, you can store the .APK anywhere on your machine and just point TC to it's location. You can also still setup an application under TestedApps if you like, pointing to where ever the file is stored. I hope this helps!629Views0likes0CommentsRe: In Headless Testing some of the priority values are different compared to regular GUI Testing
HiUttham! 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!691Views0likes1CommentRe: chrome is disabling smartbear extension when runs a jenkin job
HiAyesha! Is it possible that the Chrome instance being launched by TestComplete is using an alternate profile than the one you use when you launch it manually? It could be an issue where the profile being used doesn't have that extension installed. I would start by verifying that first.1.3KViews0likes1CommentRe: Unable to connect to BitBar via automation script using appium + NodeJS + WebdriverIO
HiMrunalCTS! 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.2 years agoPlace BitBar QuestionsBitBar Questions992Views0likes2CommentsRe: BitBar exploratory testing
Hipraveen_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!2 years agoPlace BitBar QuestionsBitBar Questions602Views0likes0CommentsRe: Appium server error com.testroid.api.APIException: Failed to submit test run! No device model match
Hinadavgivoni! 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!2 years agoPlace BitBar QuestionsBitBar Questions755Views0likes0CommentsRe: Unable to connect Appium Inspector(Web version) to session with Bitbar device
HiJasodhara! 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!2 years agoPlace BitBar QuestionsBitBar Questions709Views0likes0CommentsRe: Running tests parallelly using selenium in CBT on iphone devices - need help troubleshooting
Hileokleok! As for which devices are being used for the parallel sessions, this is going to be determined within your scripts. Each session that is started will require the specific capabilities defined in your script, so you will have full control over which devices are being utilized. For the errors, this is commonly seen most when hitting the maximum parallel limit of your subscription. We have a 6 minutes timeout, which matches the timeframe listed in your post. For instance, if you have 4 max parallel, you may launch 8 tests, but only the first 4 will receive a device session. The rest will queue until the first batch of tests end. If this time period is greater than 6 minutes your queued tests will fail. If you can/want to post your script to see how you are are launching these tests I can take a look and provide insight on devices. In the meantime I would make sure you are not going over your max parallel limit beyond 6 minutes.998Views0likes0CommentsRe: Running Selenium scripts on iPhone Safari
Hileokleok, Glad to hear you resolved the first issue. We'll take a look into that. As for parallel testing, this is all setup within your local scripts in regards to the devices used. Below is an overview of parallel testing along with some samples to help you out. Parallel Testing in CrossBrowserTesting; https://support.smartbear.com/crossbrowsertesting/docs/automated-testing/parallel-testing.html2.3KViews0likes0Comments