LF-3057 Test Plan

Owned by Denis Dovganyuk
Last updated: Mar 28, 2023
2 min read

https://lite-farm.atlassian.net/browse/LF-3057

Currently if the user creates a new irrigation task with the location that has a default irrigation type already established , it is observed that irrigation_type_id is not included in the Payload. The existing irrigation type is regarded as a new type, and a new record is added to the irrigation_type table. (A new type should be added only when the user selects “Other”)

Area / scope to test

Front end

Back end

Model

Notes

Area / scope to test

Front end

Back end

Model

Notes

Requirement specific constraints

  • Test as per Jira Ticket

  • irrigation_type_id should be included in the Payload ,of the POST /task/irrigation_task API, and a new irrigation type should not be created.

Check if in the database assigned irrigation_type_id is the same , when the user interacts with the field “Type of Irrigation” and when this field is filled with the default irrigation type that was already established.

 

Role based constraints

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

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

 

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

Text input constraints

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

 

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

 

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

Timezone driven interactions

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

 

Is the UI transitioning appropriately? Is the API providing da

Flow based constraints

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

 

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

 

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

Data transformation correctness

N/A

N/A

 

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

Outcome correctness

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

 

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

Notification constraints

N/A

N/A

 

Should a notification be marshalled based on this action?

Cascading effects

N/A

N/A

 

Are there logical places

Integration constrains

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?