LF-3370 Test Plan

Owned by Denis Dovganyuk
Last updated: Jul 10, 2023
2 min read

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

 

 

Area / scope to test

Front end

Back end

Model

Notes

Area / scope to test

Front end

Back end

Model

Notes

Requirement specific constraints

  • Ensure that all new UI elements visible as per Jira ticket

  • Testing cascading effects

 

  • Ensure that the information is stored correctly in the database.

 

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

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

  • Ensure that the page is in the users prefered language or the Missing tag 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

Per UI, user must…

.. see the following:

  • Appended to the crop plan name…

    • An underlined hyperlink showing (X/Y) where…

      • X is this plans order in the repeated sequence

      • Y is the total number of plans repeated in the sequence

  • The user should be able to see the following transitions:

    • None

The user should be able to perform the following actions:

  • Click the hyperlink to generate all the repeated crop plans

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 can still complete the crop plan

  • Ensure that the user can still abandon the crop plan

  • Ensure that the user can still Add/ Complete / Abandon / Delete tasks in the crop plan

N/A

N/A

Are there logical places

Integration constraints

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?