LF-2970 Test Plan

Owned by Denis Dovganyuk
Last updated: Mar 29, 2023 by Mwayanjana Bolokonya (Unlicensed)Version comment
2 min read

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

Currently , when the user is unable to perform a certain task ( In our case : The User is not able to register his farm )
An error message is displayed with the following text : “ Failed to add farm please contact litefarm for assistance”


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

N/A

N/A

 

Role based constraints

N/A

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

  • Error message should be in the users preferred language or MISSING tags should exist

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

  • When the user is unable to perform a certain task the correct error message should appear : “Failed to add farm, contact support? support@litefarm.org)

  • The “Copy” icon should be displayed

  • Clicking the link should open the user’s email client with the following qualities:

  • Clicking the copy icon should add “support@litefarm.org” to the clipboard

  • Snack bar should not auto-dismiss (or should have a very high secondToDismiss)

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

N/A

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?