LF-3592 Test Plan

Owned by Denis Dovganyuk
Aug 31, 2023
3 min read

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

 

Area / scope to test

Front end

Back end

Model

Notes

Area / scope to test

Front end

Back end

Model

Notes

Requirement specific constraints

  • Testing as per Jira ticket

  • Testing cascading effects during the creation

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

  • Ensure that in the database all information will be stored correctly

 

Role based constraints

  • Ensure that only FO / FM / EO are able to create custom revenue type

  • FW should not be able to enter this screen.

  • Ensure that FW is not able to create custom revenue type using API tool(Postman)

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 correctly in the user prefered language or the “MISSING” tags should exist.

  • Ensure that the certification status doesn’t impact on the fact that the user is able to create the custom revenue type

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

  • Ensure that the user is able to name the revenue using letters from the non latin alphabite.

  • Ensure that in the field “Value” the user is not able to input a “String”

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 create a custom revenue that will be in the future

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

  • Ensure that the timezone doesn’t play role and the date should always be stored and converted in UTC.

N/A

In the database make a check of this fact that the date is stored and converted appropriately.

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

Interaction / transitioning UI based constraints

  • Ensure that once the user goes back and than goes forward all the information that was filled previously should remain.

  • Ensure that the user can complete the flow once he goes back and the forth.

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 the custom revenue type can be used accross the farms and across the accounts.

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 can’t complete the flow once he won’t fill all the required fields.

  • Ensure that the pop up confirmation message will be displayed once the user clicks on the “CANCEL” button

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?