LF-3393 Test Plan

Requirement specific constraints

• Testing as per Jira Ticket

• Testing Cascading Effects

N/A

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

Role based constraints

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

• Ensure that the FW is not able to enter the crop plan completion flow

Ensure that via API tool( postman ) the user is not able to complete the crop plan as a FW

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 system of measurement prefernces ( Metric / Imperial ) doesn’t matter on the completion flow

• Ensure that the Certification status doesn’t play role .

N/A

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

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

• Ensure that the user is able to finish the task if in his local timezone (For ex. UTC + 5 ) is already 00.00AM while in UTC is still the previous day.

N/A

• Ensure that the data is correctly stored in UTC data format

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

• Ensure that the user is still not able to complete the crop plan if the completion date is in the future

• Ensure that the user is still able to complete the crop plan if the completion date is Current date or the day in the past

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

N/A

N/A

N/A

Is the UI transitioning appropriately? Is the API providing da

Flow based constraints

• Ensure that the data is still preserved appropriately if the user goes back and then forth.
  the data should maintain

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 is still able to abandon the crop plan

• Ensure that the user is still able to add new tasks to an already existing crop plan

• Ensure that if the crop plan has tasks that hasn’t been completed yet , than such crop plan can’t be completed , the error pop up message should be displayed.

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?