The PAM authentication code included in terminal and file manager is now being invoked on phablet devices in CI, due to the password/pin security being set. In the future this will be required for developer mode as well (which is required for adb and in general for test runs).
These security requirements need to account for testability in order to be able to run tests on the applications in the following ways:
1) Test the app under security. Verify the dialog loads, can be authenticated into and the app is functional
2) Test the app under no security. Run the current set of tests.
For now, CI and these tests are broken on a phone running with security pin or password set.
The PAM authentication code included in terminal and file manager is now being invoked on phablet devices in CI, due to the password/pin security being set. In the future this will be required for developer mode as well (which is required for adb and in general for test runs).
These security requirements need to account for testability in order to be able to run tests on the applications in the following ways:
1) Test the app under security. Verify the dialog loads, can be authenticated into and the app is functional
2) Test the app under no security. Run the current set of tests.
For now, CI and these tests are broken on a phone running with security pin or password set.