LF-3421 Test Plan

Requirement specific constraints

• Testing as per Jira ticket

• Ensure that per UI the element is presented , and the modal is clickable

• Ensure that once the repeated crop plan was created the information is correctly stored in the database

Role based constraints

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

• Ensure that FW is not able to enter this creation flow

• Ensure via API that the FW is not able to create the repeated crop plan

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 farm that is serching for certification is able to complete this flow.

• Ensure that the farm that is not searching for certification is able to complete the flow

• Ensure that the component is correctly displayed in different languages or “MISSING” tag should exist

Ensure that the data is correctly stored in the Database ( For Example :
If the system of measurement is Imperial, ensure that in the Database the data is converted appropriately to the Metric system of measurement )

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

Ensure that the data is stored correctly in UTC

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

Interaction / transitioning UI based constraints

• Ensure that per UI the component is visible

• Ensure the selected day is highlighted, while others are greyed.

N/A

N/A

Is the UI transitioning appropriately? Is the API providing da

Flow based constraints

• Ensure that the data would be stored 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

• Ensure that the notification would be created once the user completes the flow

N/A

N/A

Should a notification be marshalled based on this action?

Cascading effects

• Ensure that the user is able to complete the flow

• Ensure that the user is able to complete the tasks that were created during this flow.

• Ensure that the user is able to abandon tasks that were created during this flow.

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?