LF-3001 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

• Ensure that FO / FM / EO are able to access this page

• Ensure that the FW is not able to access this page

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

• Ensure that the system of measure doesn’t matter it is shown correctly in the both systems of measurement.

• Ensure that certification status doesn’t matter.

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

• Per UI user must see the following:

  • Add a "Total harvest to date" input field on crop plans

  • Label and read-only input: “Harvest to date”

    • Value should be generated based on the summed weight of all completed harvest tasks that had been made against that crop plan

    • Info text to the right of the label: “Harvest to date is calculated based on completed harvest tasks within this crop plan.”

N/A

N/A

Is the UI transitioning appropriately? Is the API providing da

Flow based constraints

N/A

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

N/A

N/A

N/A

Should a notification be marshalled based on this action?

Cascading effects

• Ensure that the user can still update the crop plan details

• Ensure that the user can still delete / abandon tasks in the created crop plan

• Ensure that when the user completes the task that is associated with a crop plan all the data is displayed correctly

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?