LF-3377 Test Plan

Requirement specific constraints

• Ensure that all UI elements are visible as per Jira Ticket

• Ensure that the user is able to create the repeated crop plan via Postman

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

Role based constraints

• Ensure that FO / FM / EO are able to create the repeated crop plan

• Ensure that FW is not able to create a repeated crop plan

• Ensure that FW is not able to create a repeated crop plan Via API TOOL ( POSTMAN )

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 the user of a farm without a certification can create a repeated crop plan

• Ensure that the user of a farm that is searching for certification can create a repeated crop plan

• Ensure that all the copies are in user prefered language or “MISSING” tag should exist

• Ensure that the system of measurement doesn’t matter( Metric or Imperial )

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

• Ensure that the pop up window would display once the user firstly created the repeated crop plan

Per UI, user must…

.. see the following:

• Background

  • “(X/Y)” on a crop plan highlighted

• Foreground:

  • Title: “Congrats! You’ve created your first repeating crop plan!”

    • Body: “You can click here to see all crop plans in this group. Modifying an individual crop plan won’t change anything about others in the group.”

    • Button: “Got it!”

User should be able to perform the following actions:

• Click anywhere on the background to dismiss the modal

• Click “Got it!” to dismiss the modal

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

N/A

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?