LF-3586 Test Plan

Requirement specific constraints

• Testing as per Jira ticket

• Ensure that all the UI elements are visible as per Jira ticket. and Figma designs.

• Testing cascading effects

• Ensure that the user is able to create a custom revenue type using the API tool.

• Ensure that in the database the information is displayed correctly

Role based constraints

• Ensure that the FW is not able to enter this page navigating through the web app.

• Ensure that the FW is not able to enter this view just by Pasting the link

• Ensure that the FO/FM/ EO are able to enter this page and create the revenue.

• Ensure that the FW account is not able to see this page using the 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 the page is displayed on the user prefered language or the “Missing” tag exist.

• Ensure that the certification status of the farm doesn’t play role and all the info is displayed correctly.

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 all the UI elements are displayed as per Figma designs.

• Ensure that the user will be prompted with informative message once he created the new revenue type.

• Ensure that the user is not able to create the revenue type without filling all the required fields.

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

• Ensure that the same name of revenue type can be used across the farms.

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 not able to rename the custom revenue type to anything that already exists in the farm

• Ensure that the user is able to edit the custom revenue type

• Ensure that the user is able to retire the custom revenue type

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 the white screen won’t be displayed to any user if the user 1 retired the custom revenue type , and the user 2 is trying to edit the same custom revenue type

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?