LF-3060 Test Plan

Requirement specific constraints

• Testing per Jira ticket

• Testing Cascading effects

N/A

• Ensure that in the database all the information is stored correctly

Role based constraints

• Only the following should see this screen:

  • Assignee of the task (if they are the creator of the task)

  • Creator of the task (if the assignee is a user without an account)

N/A

N/A

Does role determine what a user can see or do? Is this enforced uniformly across the front end and back end?

User preferences constraints

• Ensure that user or farm preferences doesn’t play role during the creation flow

N/A

N/A

Is this impacted by user or farm preferences such as language, system of measure, certification status?

Numerical input constraints

N/A

N/A

N/A

Do we appropriately handle negative, very small, very large, or 0 as inputs?

Text input constraints

N/A

N/A

N/A

Do we appropriately handle blank, very small, and very large inputs? Is there a strict format (such as email) that must be followed?

Date based constraints

N/A

N/A

N/A

Are there logical restrictions on what dates can be input? Should a use be able to complete something in the future for example.

Date based assumptions

N/A

N/A

N/A

Are we making valid assumptions about what dates should be allowed?

Timezone driven interactions

N/A

N/A

N/A

If timezones play a role in the data, are they being displayed or converted appropriately?

Interaction / transitioning UI based constraints

• Once the user clicks on the save button he should see the following

  • Interactive LiteFarm header (as described in LF-375 - Getting issue details... STATUS )

  • Title with back arrow: “Complete a task” and “Cancel” link

  • Progress bar component

    • Set at 0%

  • Body text: “Your task has been saved. Do you want to mark it as completed now?”

  • Primary button: “Mark Complete”

  • Secondary button: “Not now”

  • Must display LF-1032 - Getting issue details... STATUS from successful POST

N/A

N/A

Is the UI transitioning appropriately? Is the API providing da

Flow based constraints

User should be able to perform the following actions:

• Click “<“ to return to wherever this flow was started from and discard state

• Click “Cancel“ to:

  • Pop-up LF-1461 - Getting issue details... STATUS (flow name “task completion”) and await confirmation from the user

    • On confirmation of cancel, return to wherever this flow was started from and discard state

    • Otherwise, take no action

• Click “Mark complete” to enter the type specific completion flow (generally described in LF-1802 - Getting issue details... STATUS )

• Click “Not now” to return to return to wherever this flow was started from and discard state

N/A

N/A

Is state being preserved appropriately in a flow? If I go back and then forth, is it maintained? Is state invalidated when it should be?

Synchronous / asynchronous constraints

N/A

N/A

N/A

Is the interaction synchronous, asynchronous, or does it support both? Can you simulate both if so?

Time-out / low bandwidth constraints

N/A

N/A

N/A

Does the feature fail gracefully under no bandwidth / low bandwidth environments?

Data transformation correctness

N/A

N/A

N/A

Are values appropriately updated when units change? Is it WYSIWYG?

Outcome correctness

N/A

N/A

N/A

When inputting known inputs with expected outputs - do you get the results you expect? Have you tested several “cases” of this?

Switching farms

N/A

N/A

N/A

Does this feature respond well to switching farms (and returning)?

Notification constraints

• Ensure that the notification is displayed after the user creates the task

• Ensure that the notification is still displayed after the user completes the task

N/A

N/A

Should a notification be marshalled based on this action?

Cascading effects

• Ensure that the user can still complete the created task with making changes during the completion flow

• Ensure that the user can still complete the created task without making changes during the completion flow

• Ensure that the user can still abandon the created task

• Ensure that the user can still delete the created task

N/A

N/A

Are there logical places

Integration constrains

N/A

N/A

N/A

Do we need to ensure state is consistent between LiteFarm and the external service? What failure cases do we need to handle? How do we report back the outcome to the user or external service?

Concurrency

N/A

N/A

N/A

How do changes made to records affect other users on the farm? e.g. What happens when a record is soft deleted while another user is viewing said record?