Page Comparison

Requirement specific constraints

• Ensure all units displays is in the task creation user flow display values as intended

• Ensure all units displays in the location creation user flow display values as intended

• Ensure all non measurement unit displays i.e. currency displays in task user flow display correctly

N/A

• Ensure values stored in the database correctly reflect the values entered via the front end

Role based constraints

N/A

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 all units displays, display values in both imperial and metric systems correctly

• Ensure data input via units displays in both imperial and metric measurement systems is persisted consistently and as intended in the database

Is this impacted by user or farm preferences such as language, system of measure, certification status?

Farm-level defaults / preferences

Numerical input constraints

• Ensure input validation still works as intended for all units displays

Do we appropriately handle negative, very small, very large, or 0 as inputs?

Text input constraints

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

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

Are we making valid assumptions about what dates should be allowed?

Timezone driven interactions

If timezones play a role in the data, are they being displayed or converted appropriately?

Interaction / transitioning UI based constraints

• Ensure interaction with units displays(change from m to km/ l to m^3) functions as intended

Is the UI transitioning appropriately? Is the API providing da

Flow based constraints

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

Is the interaction synchronous, asynchronous, or does it support both? Can you simulate both if so?

Time-out / low bandwidth constrains

Does the feature fail gracefully under no bandwidth / low bandwidth environments?

Data transformation correctness

Are values appropriately updated when units change? Is it WYSIWYG?

Outcome correctness

When inputting known inputs with expected outputs - do you get the results you expect? Have you tested several “cases” of this?

Switching farms

Does this feature respond well to switching farms (and returning)?

Notification constraints

Should a notification be marshalled based on this action?

Cascading effects

• Ensure calculations based on unit display inputs yield the correct the correct outcomes:

  • Water usage calculations

  • Finance calculations

  • Harvest yield calculations

Are there logical places

Integration constrains

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?