ContributionsMost RecentMost LikesSolutionsBitbar Screen Capturing For some device screen capture is not happing.any region for that. Re: Application performance using BITBAR But there might be possibility to do such measurement on the tests level,how can we measure. Re: Device Behavior details https://cloud.bitbar.com/#testing/device-session/207035746/207084291/4642063 In this test run there is no performance.json Application performance using BITBAR Hi All, Can we able to get page load time after every actions.(App level) Testcase 1: Login to Driver application Steps: 1. Enter username and password 2.Click on submit button Expected result:Should display the driver dashboard In above test case we are giving username and password and clicking on submit button After click action(in back end It will get data from api) then display in the UI. We want to know the response time for Page loading after every actions. Device Behavior details We want to test our application performance , so how can we get, In device Behavior its contains device waiting,preparing,installing,Running,Sending results,Processing results, what exactly which includes only application or not. Need help to run automated test using Bitbar Need to run the automated test with ruby and appium with cucumber framework getting some issues as Appium REST http interface listener started on 0.0.0.0:4723 2019-12-04 09:47:04:394 - [HTTP] --> POST /wd/hub/session 2019-12-04 09:47:04:394 - [HTTP] {"desiredCapabilities":{"platformName":"Android","automationName":"Appium","appPackage":"com.rttdriver","deviceName":"Android device","app":"/test"},"capabilities":{"firstMatch":[{"platformName":"Android","appium:automationName":"Appium","appium:appPackage":"com.rttdriver","appium:deviceName":"Android device","appium:app":"/test"}]}} replace run-tests.sh? [y]es, [n]o, [A]ll, [N]one, [r]ename: NULL (EOF or read error, treating as "[N]one" ...) inflating: setup_appium.rb linking: TEST-all.xml -> *.xml finishing deferred symbolic links: TEST-all.xml -> *.xml Starting Appium ... 2019-12-04 09:47:04:396 - [debug] [W3C] Calling AppiumDriver.createSession() with args: [{"platformName":"Android","automationName":"Appium","appPackage":"com.rttdriver","deviceName":"Android device","app":"/test"},null,{"firstMatch":[{"platformName":"Android","appium:automationName":"Appium","appium:appPackage":"com.rttdriver","appium:deviceName":"Android device","appium:app":"/test"}]}] 2019-12-04 09:47:04:396 - [debug] [BaseDriver] Event 'newSessionRequested' logged at 1575452824396 (09:47:04 GMT+0000 (Coordinated Universal Time)) 2019-12-04 09:47:04:403 - [Appium] 2019-12-04 09:47:04:403 - [Appium] ====================================================================== 2019-12-04 09:47:04:403 - [Appium] DEPRECATION WARNING: 2019-12-04 09:47:04:403 - [Appium] 2019-12-04 09:47:04:403 - [Appium] The 'automationName' capability was not provided in the desired 2019-12-04 09:47:04:404 - [Appium] capabilities for this Android session 2019-12-04 09:47:04:404 - [Appium] 2019-12-04 09:47:04:404 - [Appium] Setting 'automationName=UiAutomator2' by default and using the 2019-12-04 09:47:04:404 - [Appium] UiAutomator2 Driver 2019-12-04 09:47:04:404 - [Appium] 2019-12-04 09:47:04:404 - [Appium] The next major version of Appium (2.x) will **require** the 2019-12-04 09:47:04:404 - [Appium] 'automationName' capability to be set for all sessions on all 2019-12-04 09:47:04:404 - [Appium] platforms 2019-12-04 09:47:04:404 - [Appium] 2019-12-04 09:47:04:404 - [Appium] In previous versions (Appium <= 1.13.x), the default was 2019-12-04 09:47:04:405 - [Appium] 'automationName=UiAutomator1' Solved