LF-3296 Test Plan

Requirement specific constraints

• Testing as per Jira ticket

• Testing cascading effects

• Ensure that the error is not displayed both via the APP and via API (Postman)

• Ensure that In the Database all the information is stored correctly after completing the task

Role based constraints

• Ensure that all the users can complete the field work task if the task is assigned to them

• Ensure that non of the users can complete the task if the task is assigned to any other user.

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

• Ensure that farm or user preferences don’t impact on the completing of the Field Work Task

  • Change the language to any else than English

  • Change the system of measure

  • Change the certification status

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

• Ensure that the data is converted appropriately in the database

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 information is preserved appropriately in a flow

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 is still displayed after the user completes the field work task

N/A

N/A

Should a notification be marshalled based on this action?

Cascading effects

• Ensure that the user is still able to complete the field work task without making any changes in any of the fields.

• Ensure that the user is still able to complete the field work task while making some changes during the 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

• Ensure that the status of the field work task is updated accordingly to the both users in the farm

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?