LF-3009 Test plan

Requirement specific constraints

• All new UI elements visible as per Jira ticket

N/A

N/A

Role based constraints

• FO/FM/EO should see the “Delete task” link

• FW should not see the “Delete task” link

• FW shouldn’t be able to download template

• FW shouldn’t be able to upload template

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

• Copy should be in the users preferred language or MISSING tags should exist

• 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

• When user clicks on “Delete task” for a planting task, the user should be redirected to the planting task view

• When user clicks on “Delete task” for any other task type, the user should be redirected to the standard task delete view

• On the planting view if the user clicks “abandon crop plan” navigate to the management plan details view for the parent crop plan

• if the user clicks cancel on the planting task view. redirect back to the default view

• if the user clicks “confirm deletion” on the standard delete view

• If a deleted task was assigned to a user a notification is generated notifying said user that the task was deleted

• FM/FO/EO should be able to PATCH delete task

• FW should not be able to PATCH delete task

• When a user clicks “confirm deletion” deleted should be set to true in the task table

Is the UI transitioning appropriately? Is the API providing da

Flow based constraints

• Deleted tasks are not displayed in the tasks list view, parent crop plan task view, exports under record D or I

• Deleted tasks are not included in calculations under labour expenses or revenue

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

• When notification is received, data should be available in the database

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

• On successfully setting a task as deleted a snackbar is displayed as per LF-1032 - Getting issue details... STATUS

• Success: returns 400

• Errors:

  • Code varies by reason

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

• Notification generated for task deletion is displayed correctly as per UI requirements

• N/A

• N/A

Should a notification be marshalled based on this action?

Cascading effects

• N/A

• N/A

Are there logical places

Integration constrains

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?