LF-3628 Test Plan

Requirement specific constraints

• Testing as per Jira ticket

• Testing cascading effects

• Ensure that all the UI elements are visible as per Jira ticket

• Ensure that the user is able to patch an individual revenue using API tool( Postman)

• Ensure that after editing all the information is correctly displayed in the database

Role based constraints

• Ensure that FW is not able to enter this Page.

• Ensure that FO/FM/EO are able to update the individual revenuee

• Ensure that the FW is not able to edit the revenue using API tool

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 all the information is displayed in the user prefered language or the “Missing” tag should exist

• Ensure that the certification status of the farm doesn’t play role.

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

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

N/A

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

Interaction / transitioning UI based constraints

• Ensure that the read only view has all the required UI elements as per Jira ticket.

• Ensure that once the user clicks on the “Edit” button he should be redirected to the “Edit” view of the Revenue.

• Ensure that when the user clicks on the “Delete Revenue type” the confirmation pop up message should be displayed to him

• Ensure that the user is able to edit “Crop based revenue”detail flow

• Ensure that the user is able to edit “NON crop based revenue” detail flow

N/A

N/A

Is the UI transitioning appropriately? Is the API providing da

Flow based constraints

N/A

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 edit/delete the custom revenue category.

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

• Ensure that there won’t be any white screens once one user deletes the custom revenue , and the other user tries to edit it.

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?