Faulty strings in the test descriptions

Bug #457759 reported by Gabor Kelemen
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
checkbox (Ubuntu)
Fix Released
Undecided
Marc Tardif

Bug Description

Binary package hint: checkbox

https://translations.edge.launchpad.net/ubuntu/karmic/+source/checkbox/+pots/checkbox/hu/45/+translate

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/network.txt.in:26

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://doc.ubuntu.com/ubuntu/internet/C/modem-connect.html

https://translations.edge.launchpad.net/ubuntu/karmic/+source/checkbox/+pots/checkbox/hu/33/+translate

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/fingerprint.txt.in:3

This should be the "Fingerprint login verification procedure:". The unlocking is described in the next string:

https://translations.edge.launchpad.net/ubuntu/karmic/+source/checkbox/+pots/checkbox/hu/34/+translate
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/fingerprint.txt.in:21

This contains two third steps.

Related branches

Revision history for this message
Marc Tardif (cr3) wrote :

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.

Changed in checkbox (Ubuntu):
status: New → In Progress
assignee: nobody → Marc Tardif (cr3)
Marc Tardif (cr3)
Changed in checkbox (Ubuntu):
status: In Progress → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package checkbox - 0.9

---------------
checkbox (0.9) lucid; urgency=low

  [ Marc Tardif ]
  New upstream release (LP: #532882):
  * Introduced job_prompt plugin to treat all jobs (suites, tests, etc.) as composites.
  * Replaced the registry and resource scripts and centralized job iteration.
  * Replaced dependency on dbus by using sudo/gksu/kdesudo instead.
  * Replaced mktemp with mkdtemp for security purposes.
  * Fixed strings in fingerprint and modem tests (LP: #457759)
  * Fixed client side validation of Launchpad form (LP: #438671)
  * Added device information to tags when reporting bugs with apport.
  * Added shorthands for blacklist-file and whitelist-file.
  * Added support for apport default configuration (LP: #465447)
  * Added support for scrolled options list (LP: #411526)
  * Added support for tests generated by suites to run as root.
  * Added support for requirements in attachments.
  * Added support for armv7l processor
  * Added Autotest integration
  * Added LTP integration
  * Added Phoronix integration
  * Added qa-regression-testing integration
 -- Mathias Gug <email address hidden> Tue, 09 Mar 2010 16:58:36 -0500

Changed in checkbox (Ubuntu):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.