Page Comparison

Requirement specific constraints

• Testing as per Jira TicketTesting Cascading Effects

• Ensure that the new Number input component works as it should

N/A

• Ensure that in the database all the information is correctly displayed.

Role based constraints

• Ensure that only FO / EO / FM are able to enter this flow.

• Ensure that FW is not able to enter this flow directly from the link .

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 the language preferences doesn’t play role or the Missing Tag should exist

• Ensure that the certification status of the farm doesn’t play role

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

Label: “Repeat every”

• Number selector

  • Default value: 1

  • Value range: 1 - 50

  • Required

• Label: “Finish”

  • Radio buttons

    • Label and number selector: “After <X> repetitions”

      • Default value: 3

      • Value range: 1 - 20

      • Required

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 UI components are displayed correctly , and the user can interact with this modal

• Ensure that when the user hover the mouse over the “^” the background should be darken

• Ensure that when the user clicks on the stepper control “^”the number will be increased by the number of clicks on this component

N/A

N/A

Is the UI transitioning appropriately? Is the API providing da

Flow based constraints

• Ensure that the date would be preserved appropriately if the user goes back and then forth

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?