Page Comparison

Requirement specific constraints

• Testing per Jira ticket

• Testing Cascading effects

• On the last screen of the “Create a crop plan” flow we will add a link “+ Repeat this crop plan” which will open the pop-up from ticket

  Jira Legacy
  server System JIRA serverId 815f41e5-e5fb-3402-8587-82eccc3ffab0 key LF-3362

  . Once the repeating offset is set and the user clicks “Save” a modal will apear so they can check the information of the offset they just created.

  This transition/interaction will be the same as the “Delete” interaction for tasks.

• Ensure that the user is able to create a repeating crop plan using API tool ( Postman )

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

Role based constraints

• Ensure that only FO / FM / EO are able to indicate a crop plan

• Ensure that FW is not able to enter this flow

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

N/A

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:

• If the crop plan does not have a repetition:

  • Label and link: “+ Repeat this crop plan”

• If the repeat crop plan flow has already been created:

  • Repeated crop plan card (as described in

    Jira Legacy
    server System JIRA serverId 815f41e5-e5fb-3402-8587-82eccc3ffab0 key LF-3365

    ) with the properties as entered on

    Jira Legacy
    server System JIRA serverId 815f41e5-e5fb-3402-8587-82eccc3ffab0 key LF-3362

N/A

N/A

Is the UI transitioning appropriately? Is the API providing da

Flow based constraints

User must be able to see the following transitions:

• None

 User must be able to perform the following actions:

• Click “+ Repeat this crop plan” opens the modal defined in

  Jira Legacy
  server System JIRA serverId 815f41e5-e5fb-3402-8587-82eccc3ffab0 key LF-3362

• Click “Save” to save the state to the store and persist to the database (as described in

  Jira Legacy
  server System JIRA serverId 815f41e5-e5fb-3402-8587-82eccc3ffab0 key LF-1348

  )

  • If a crop plan is repeated, use the functionality described in

    Jira Legacy
    server System JIRA serverId 815f41e5-e5fb-3402-8587-82eccc3ffab0 key LF-3363

• Click “Modify” or “Cancel repetition” on the repeating crop plan card (as described in

  Jira Legacy
  server System JIRA serverId 815f41e5-e5fb-3402-8587-82eccc3ffab0 key LF-3365

  ) to take the actions defined in that story

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 re - assign the created crop plan tasks to anybody else in the farm

• Ensure that the user can still complete the created task without making any changes in the task

• Ensure that the user can still complete the created task with making any changes in the task

• Ensure that the user can still abandon the created task in the crop plan

• Ensure that the user can still delete the created task in the crop plan (Except Planting 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?