How to reproduce:
1) Have an existing BlackBerry device registered in 'Tools -> Options... -> Devices' page.
2) Select the BlackBerry device in 'Device' combobox.
3) Consider two options that an user might have or might not have pressed 'Connect to device' button already
3) Click on 'Test' button

Similar action is automatically run when you add a new BlackBerry device too.

Expected behavior:
The device tester will not be available since we cannot verify that a device is working unless the device is connected.
Or if possible, the device tester should be working and automatically connecting to a device if needed. Then the device tester should be able to check if the device is working and registered correctly.

Actual behavior:
The device tester always fails.

If an user does not connect to a device yet, then the error message is:
=================
Connecting to host...
SSH connection failure: Connection refused

Device test failed.
=================

If an user connects to a device yet, then the error message is:
=================
Connecting to host...
Checking kernel version...
QNX 8.0.0 MSM8960_V3.2.1.1_F_R085_Rev:14

Checking if specified ports are available...
Error gathering ports: Remote process failed; exit code was 2.
Remote error output was: sed: can't read /proc/net/tcp: No such file or directory

Device test failed.
=================

Solution:
The root cause is that BlackBerryDeviceConfiguration is using Linux device tester which is incompatible with QNX OS.
We need to implement our own BlackBerryDeviceConfiguration::createDeviceTester() function that would:
a) automatically connect to a device if not connected already and
b) perform correct testing of a device.