[FEATURE] - Device.runPreflight(...) factory to take a "Device" as argument

[yanniel]

Is your feature request related to a problem? Please describe.

It is not possible to use the PreflightTest to troubleshoot issues that arise due to the configuration of the Twilio Device. This is because the PreflightTest.Options are a narrow subset of the Device.Options.

For instance: I cannot do a PreflightTest that enforces aggressive ICE nomination.

Describe the solution you'd like

I would like the Device.runPreflight(...) factory to take aDevice as argument. Ex:

const myDevice = new Device(twilioAccessToken, {
    codecPreferences: ["opus", "pcmu"],
     dscp: true,
     maxAverageBitrate: 16000,
     maxCallSignalingTimeoutMs: 30000,
     forceAggressiveIceNomination: true,
});

const preflightTest = Device.runPreflight(myDevice); 

Describe alternatives you've considered

None.

Additional context

None.

[charliesantos]

@yanniel thanks for submitting. Is the main reason for this feature request is because you cannot use all Device.Options when running preflight? Any other reason?

[yanniel]

@yanniel thanks for submitting. Is the main reason for this feature request is because you cannot use all Device.Options when running preflight? Any other reason?

Having the Preflight test take Device.Options would be a step in the right direction. So, I'll take it if it is easier to implement :-)

That said, that is not exactly the same as having the ability to test the Device instance that's being used to take calls in a Production environment. The latter is closer to the "truth" because it operates on the same Twilio Device used in Production whereas the Preflight test is creating another Device instance under the hood.