Fluid Engage code entry QA test plan

QA overview

Environments

• iPhone OS 3.0 or higher on iPhone 3G or 3GS
• iPhone OS 3.0 or higher on iPod touch 1G, 2G or 3G

Protocol overview

• Perform each of the tests under "QA tests" using each system environment.
• Report issues at http://issues.fluidproject.org/secure/Dashboard.jspa.
• Please search for issues before reporting them, so as to limit the number of duplicate entries.

General QA guidelines

• Does the tool behave the way that you would expect?
• Are you surprised by anything?
• Does something take longer than you would expect?
• When the tool does something unexpected or takes too long to do something, does the tool provide appropriate feedback?

QA tests

Unit tests

Protocol: Launch the following websites to execute unit tests.

url to be filled

Task-oriented functional tests

Description: Ensures that the component is able to handle expected input.

Protocol: Perform these tasks after completing initial Engage setup (to be added: instructions on adding app to home screen).

Test 1: Page load

Procedure:

1. From the application home screen, tap "Enter object code" or its icon.

Expected results:

• A back button and "Enter object code" title should appear in the navigation bar, in that order. No other elements should be present on the bar.
• Short instructions (e.g., "Enter code from the object's label to learn more about the object") should appear below the navigation bar.
• Empty fields should appear below the instructions (in the case of Engage 0.3, it should be two empty fields)
• A keypad should appear below the empty fields, which includes the numbers 0-9, and a delete key.

Test 2: Enter a single-digit (cont'd from Test 1)

Procedure:

1. Complete Test 1.
2. Tap on a number from the keypad.

Expected results:

• The tapped number should appear in the left text field.
• Nothing else should have changed.

Test 3: Delete a single-digit (cont'd from Test 2)

Procedure:

1. Complete Test 2.
2. Tap the delete key.

Expected results:

• The right-most number should disappear.
• Nothing else should have changed.

Test 4: Enter an invalid object code (cont'd from Test 1)

Procedure:

1. Complete Test 1.
2. Tap in a two-digit, invalid object code (see object code list for possibilities).

Expected results:

• An error should appear on the screen ("Invalid code. Please try again.", replacing the enter code instructions.
• The number fields should clear after a brief moment (~0.5 seconds).
• The error message should persist.

Test 5: Enter an invalid object code, again (cont'd from Test 4)

Procedure:

1. Complete Test 4.
2. Tap another two-digit, invalid object code (see object code list for possibilities).

Expected results:

• The error message from the previous invalid code should persist.
• The number fields should clear after a brief moment (~0.5 seconds).
• The error message should persist.

Test 6: Enter a valid object code (cont'd from Test 1, 4, or 5)

Procedure:

1. Complete Test 1, 4, or 5.
2. Tap a two-digit, valid object code (see object code list for possibilities).

Expected results:

• If there was an error message from a previously invalid code, it should disappear immediately.
• There should be a brief pause after the last digit is entered.
• The screen should transition to the respective artifact view.

Boundary Tests

Description: Ensures proper functionality at the input limits.

Protocol: Perform these tasks on the following site.