Page Comparison

Requirement specific constraints

All UI elements exist as per Jira ticket

N/A

N/A

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

All copy is in the user’s preferred language

N/A

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

Farm-level defaults / preferences

N/A

N/A

N/A

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

User can select any date in the past or future in “another date” radio is selected

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

• The “original due date” radio has the original due date in the pill next to the radio

• The “today” radio has the current date in the pill next to it

• If original due date is selected the completion date posted on task completion is the original due date

• If today is selected the completion date posted on task completion is the current date

• If another date is selected the date selected is the completion date posted on task completion

• If original due date is selected the complete_date is the original due date

• If today is selected the complete_date is the current date

• If another date is selected the date selected is the complete_date

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

Timezone driven interactions

Original due date and today are correct for the user(make sure to test for timezones that are a day ahead/behind)

N/A

Complete_date is persisted correctly

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

Interaction / transitioning UI based constraints

• If “original due date” or “today” are selected the date pill is also selected

• if “another date” is selected Label: “Which date?” and Input: a standard date picker are displayed

N/A

N/A

Is the UI transitioning appropriately? Is the API providing da

Flow based constraints

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 constrains

N/A

N/A

N/A

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

Data transformation correctness

Is the data persisted as expected post-transformation?

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

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?