Repository navigation
Where is the --plugin-device-farm-live-streaming command used ?? #1475
|
Where is the --plugin-device-farm-live-streaming command used?
Either way, the default value of export const DefaultPluginArgs: IPluginArgs = {
platform: 'none',
iosDeviceType: 'both',
androidDeviceType: 'both',
skipChromeDownload: true,
hub: undefined,
maxSessions: 8,
derivedDataPath: undefined,
adbRemote: [],
remoteMachineProxyIP: undefined,
proxy: undefined,
emulators: [],
simulators: [],
deviceAvailabilityTimeoutMs: 300000,
deviceAvailabilityQueryIntervalMs: 10000,
sendNodeDevicesToHubIntervalMs: 30000,
checkStaleDevicesIntervalMs: 30000,
checkBlockedDevicesIntervalMs: 30000,
newCommandTimeoutSec: 60,
cloud: undefined,
bindHostOrIp: ip.address(),
enableDashboard: false,
removeDevicesFromDatabaseBeforeRunningThePlugin: false,
remoteConnectionTimeout: 60000,
liveStreaming: true, // liveStreaming default value is true
wdaBundleId: '',
preBuildWDAPath: '',
};Additionally, when running multiple test cases continuously, I found the issue shown in the screenshot below for each test case. I suspect this is related to the second point, which is why I would like to set liveStreaming to false. This issue has also caused test execution time to become slower than before using the plugin. Please check and advise. @saikrishna321 |
Replies: 2 comments 3 replies
|
@Yoodahun, the Now for the issue related to the screenshot, we will fix it in the upcoming version. |

@Yoodahun, the
liveStreamingflag han been deprecated, and the documentation require an update. To provide context, enabling live streaming involves the plugin performing prerequisite setup at the start of each new session. This setup causes performance degradation even when live streaming isn't needed. In the latest version, we’ve introduced a new capability,df:liveVideo, which allows users to disable the live streaming setup based on their requirements during automation.Now for the issue related to the screenshot, we will fix it in the upcoming version.