Faulty strings in the test descriptions
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
checkbox (Ubuntu) |
Fix Released
|
Undecided
|
Marc Tardif |
Bug Description
Binary package hint: checkbox
Built-in modem network connection procedure: 1.- Connect the telephone line to the computer 2.- Right click on the Network Manager applet 3.- Select 'Edit Connections' 4.- Select the 'DSL' tab 5.- Click on add 'Add' button 6.- Configure the connection parameters properly 7.- Notify OSD should confirm that the connection has been established 8.- Select Test to verify that it's possible to establish both http \ and ftp connections
Located in ../tests/
So, it is really possible to create a DSL connection with a built-in 56k fax modem? :)
If I didn't missed an important innovation, then this string contains misinformation, the process should be based on this: http://
Fingerprint unlock verification procedure: 1.- Click on the user switcher applet 2.- Select your user name 3.- A window should appear that provides the ability to login either \ typing your password or using fingerprint authentication 4.- Use the fingerprint reader to login 5.- Click on the user switcher applet 6.- Select the testing account to continue running tests
Located in ../tests/
This should be the "Fingerprint login verification procedure:". The unlocking is described in the next string:
https:/
Fingerprint unlock verification procedure: 1.- Click on the user switcher applet 2.- Select 'Lock screen' 3.- Press any key or move the mouse 3.- A window should appear that provides the ability to unlock either \ typing your password or using fingerprint authentication 4.- Use the fingerprint reader to unlock 5.- Screen should be unlocked
Located in ../tests/
This contains two third steps.
Related branches
Changed in checkbox (Ubuntu): | |
status: | In Progress → Fix Committed |
It is unfortunately too late to make any string changes in Karmic but I have pushed a branch for review which should hopefully fix this bug for Lucid. Thanks for the detailed bug report.